-
Type:
Bug
-
Status: Confirmed (View Workflow)
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 5.5, 10.1, 10.2, 10.3, 10.0
-
Component/s: Storage Engine - InnoDB
-
Labels:
InnoDB is notoriously aborting the whole MariaDB server if it is trying to access a corrupted page.
MDEV-12253 alleviated the issue somewhat, but not for background processing, such as the purge of no-longer-needed history.
This bug exists in all InnoDB and XtraDB versions.
MariaDB essentially must fix MySQL Bug#10132 Crashing the server on corrupt InnoDB page is unhelpful that was filed on April 25, 2005.
In 10.3 with MDEV-12288 and MDEV-13536, the InnoDB purge threads will access pages more often, causing all sorts of debug assertion failures in the B-tree code. To work around this problem, tests that intentionally cause B-tree pages to be unreadable are amended with the following parameters, so that everything will be purged before the server is restarted to deal with the corruption:
--innodb-purge-rseg-truncate-frequency=1
|
--skip-innodb-fast-shutdown
|
- blocks
-
MDEV-18519 0x7f0118195700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.7/storage/innobase/btr/btr0cur.cc line 4308
-
- Stalled
-
-
MDEV-21098 indexes in subquery causing MariaDB crash ???
-
- Open
-
- includes
-
MDEV-22388 Corrupted undo log record leads to server crash
-
- Open
-
- is duplicated by
-
MDEV-16497 Server crashes on corrupted pages during DROP TABLE
-
- Closed
-
- relates to
-
MDEV-12112 corruption in encrypted table may be overlooked
-
- Closed
-
-
MDEV-13680 InnoDB may crash when btr_page_alloc() fails
-
- Confirmed
-
-
MDEV-17810 Improve error printout when decryption fails or we identify page as both encrypted and unencrypted
-
- Closed
-
-
MDEV-17957 Make Innodb_checksum_algorithm stricter for strict_* values
-
- Closed
-
-
MDEV-17958 Make bug-endian innodb_checksum_algorithm=crc32 optional
-
- Closed
-
-
MDEV-18025 Mariabackup fails to detect corrupted page_compressed=1 tables
-
- Closed
-
-
MDEV-18026 Make mariabackup option to double read the pages from data file.
-
- Closed
-
-
MDEV-18691 Failing assertion: page_is_comp(next_page) == page_is_comp(page) in btr0pcur.cc
-
- Closed
-
-
MDEV-18932 MariaDB 10.3.10-10.3.13 corrupts table and refuses to start with assertion in row0sel.cc 2986
-
- Closed
-
-
MDEV-19081 DB crashes periodicly with - InnoDB: Assertion failure
-
- Closed
-
-
MDEV-19541 InnoDB crashes when trying to recover a corrupted page
-
- Closed
-
-
MDEV-21030 MariaDB keepts crashing on start
-
- Closed
-
-
MDEV-21513 Fix some crashes in ALTER TABLE…IMPORT TABLESPACE
-
- Closed
-
-
MDEV-21863 InnoDB: Assertion failure rem0rec.cc 1878
-
- Closed
-
-
MDEV-22373 Unable to find a record to delete-mark ends up crashing mysqld process after upgrading from 10.1.43 to 10.4
-
- Open
-
-
MDEV-22481 Server crash after access to table with imported tablespace (after restart)
-
- Closed
-
-
MDEV-22624 mariadb used for wordpress restarts and crashes continuously
-
- Closed
-
-
MDEV-23344 InnoDB: Fatal: Trying to access page number 57 in space 182 space name zabbix/items.
-
- Stalled
-
-
MDEV-23734 InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
-
- Closed
-
-
MDEV-11125 Introduce a reduced doublewrite mode, handling error detection only
-
- Stalled
-
-
MDEV-12253 Buffer pool blocks are accessed after they have been freed
-
- Closed
-
-
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC
-
- Closed
-
-
MDEV-13536 DB_TRX_ID is not actually being reset when the history is removed
-
- Closed
-
-
MDEV-13559 encryption.innodb-redo-badkey failed in buildbot
-
- Closed
-
-
MDEV-14132 innodb.innodb-64k failed in buildbot, lost connection to server
-
- Closed
-
-
MDEV-14481 Execute InnoDB crash recovery in the background
-
- Stalled
-
-
MDEV-16763 SIGNAL 6 ERROR
-
- Open
-
-
MDEV-17482 InnoDB fails to say which fatal error fsync() returned
-
- Closed
-
-
MDEV-17638 Improve error message about corruption of encrypted page
-
- Closed
-
-
MDEV-17641 start slave and mariadb server crash
-
- Closed
-
-
MDEV-17947 mariabackup SST encounters InnoDB tablespace errors during prepare, ignores them, server crashes
-
- Closed
-
-
MDEV-18115 Remove dummy tablespace for the redo log
-
- Closed
-
-
MDEV-18529 InnoDB wrongly skips decryption of encrypted page if unencrypted and post-encrypted checksums match
-
- Closed
-
-
MDEV-18606 innodb crashes on large update and it gets corrupted
-
- Open
-
-
MDEV-19711 Assertion failure during IMPORT TABLESPACE
-
- Open
-
-
MDEV-20931 ALTER...IMPORT can crash the server
-
- Open
-
-
MDEV-24412 Mariadb 10.5: InnoDB: Upgrade after a crash is not supported
-
- Closed
-
-
MDEV-24578 MariaDB 10.5 fails to join Galera cluster of MariaDB 10.1, root cause SST failure, symptom is InnoDB: Assertion failure
-
- Open
-
- links to