Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Description
Since the very first version, InnoDB was aborting the whole MySQL or MariaDB server when trying to access a corrupted page.
Earlier, small steps have been taken to improve MariaDB stability, such as MDEV-12253.
We must enable error handling for corrupted pages instead of allowing the server to crash. This is not only about detecting a checksum failure when reading a corrupted page (like suggested in MySQL Bug#10132 Crashing the server on corrupt InnoDB page is unhelpful, filed on April 25, 2005), but also about performing some operations on corrupted pages whose checksum appears valid.
In some background operations, such as the purge of committed transaction history, errors may be reported to the server error log only, or silently ignored. While executing SQL, errors should be reported back to the client, and the transaction could be rolled back.
Attachments
Issue Links
- blocks
-
MDEV-18519 0x7f0118195700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.7/storage/innobase/btr/btr0cur.cc line 4308
- Closed
-
MDEV-18976 Implement a CHECKSUM redo log record for improved validation
- Closed
-
MDEV-21098 Crash in rec_get_offsets_func() due to invalid rec_get_status()
- Closed
-
MDEV-22388 Corrupted undo log record leads to server crash
- Closed
-
MDEV-27593 Crashing on I/O error is unhelpful
- Closed
-
MDEV-28457 Crash in page_dir_find_owner_slot()
- Closed
-
MDEV-29603 btr_cur_open_at_index_side() is missing some consistency checks
- Closed
-
MDEV-34830 LSN in the future is not being treated as serious corruption
- In Progress
- causes
-
MDEV-28845 InnoDB: Failing assertion: bpage->can_relocate() in buf0lru.cc
- Closed
-
MDEV-28950 Assertion `*err == DB_SUCCESS' failed in btr_page_split_and_insert
- Closed
-
MDEV-29321 Percona XtraDB 5.7 can't be upgrade to MariaDB 10.6 or above
- Closed
-
MDEV-29374 Frequent "Data structure corruption" in InnoDB after OOM
- Closed
-
MDEV-29383 Assertion mysql_mutex_assert_owner(&log_sys.flush_order_mutex) failed in mtr_t::commit()
- Closed
-
MDEV-29435 CHECK TABLE forgets to release latches after reporting failure
- Closed
-
MDEV-31333 fsp_free_page() fails to move the extent from FSP_FREE_FRAG to FSP_FREE list
- Closed
- is duplicated by
-
MDEV-14170 InnoDB: Failing assertion: sibling_mode == RW_NO_LATCH || btr_page_get_next(get_block->frame, mtr) == page_get_page_no(page)
- Closed
-
MDEV-16497 Server crashes on corrupted pages during DROP TABLE
- Closed
-
MDEV-26550 [FATAL] [ERROR] mysqld got signal 6 ;InnoDB: Aborting because of a corrupt database page.
- Closed
-
MDEV-27865 buf_page_read_complete assertions during during innodb_init
- Closed
-
MDEV-28148 InnoDB slave crash / signal 6
- Closed
-
MDEV-28574 Assertion failure in fil_invalid_page_access_msg() while running CHECK TABLE to find the details on corruption suspected
- Closed
-
MDEV-28786 InnoDB crash leads to pagesize comparison failure
- Closed
-
MDEV-29126 DB is crashing repeatedly with error message "InnoDB: Rec offset 99, cur1 offset 1723, cur2 offset 16095"
- Closed
-
MDEV-29130 InnoDB: Assertion failure in file storage/innobase/fsp/fsp0fsp.cc line 1562
- Closed
-
MDEV-29150 DB continuously rebooting
- Closed
-
MDEV-33398 Server crashes when executing DML with innodb_checksum_algorithm set to strict_innodb
- Closed
- relates to
-
MDEV-12112 corruption in encrypted table may be overlooked
- Closed
-
MDEV-13680 InnoDB may crash when btr_page_alloc() fails
- Closed
-
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
- Closed
-
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.
- Closed
-
MDEV-23734 InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
- Closed
-
MDEV-26780 Tablespaces corrupt, MariaDB does not start
- Closed
-
MDEV-26893 innodb assertion on startup - rem0rec:877
- Closed
-
MDEV-28143 Data table corruption/crashing on btrfs
- Open
-
MDEV-28975 AWS RDS mariadb 10.5.12 crashes upon OS update
- Closed
-
MDEV-29082 InnoDB: Failing assertion: !cursor->index->is_committed()
- Closed
-
MDEV-29938 InnoDB: Assertion failure in btr0pcur.cc line 532
- Open
-
MDEV-30132 Crash after recovery, with InnoDB: Tried to read ... bytes at offset
- Closed
-
MDEV-31353 InnoDB recovery hangs after reporting corruption
- Closed
-
MDEV-32269 InnoDB after ALTER TABLE…IMPORT TABLESPACE may not be crash safe
- Closed
-
MDEV-33325 Crash in flst_read_addr on corrupted data
- Closed
-
MDEV-9663 InnoDB assertion failure: *cursor->index->name == TEMP_INDEX_PREFIX, or !cursor->index->is_committed()
- Closed
-
MDEV-11125 Introduce a reduced doublewrite mode, handling error detection only
- Closed
-
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
- Closed
-
MDEV-16763 SIGNAL 6 ERROR
- Closed
-
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
- Closed
-
MDEV-19711 Assertion failure during IMPORT TABLESPACE
- Closed
-
MDEV-20931 ALTER...IMPORT can crash the server
- Closed
-
MDEV-24287 mysqlcheck unexpectedly causes table to be marked as corrupt
- Closed
-
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
- Closed
-
MDEV-26022 InnoDB page data size mismatch crash
- Closed
-
MDEV-26537 InnoDB corrupts files due to incorrect st_blksize calculation
- Closed
-
MDEV-27053 Crash on assertion failure in btr0cur.cc - apparent index corruption
- Closed
-
MDEV-27538 MariaDB server startup crash
- Closed
-
MDEV-28002 Failing assertion: btr_page_get_prev(next_page, mtr) == btr_pcur_get_block(cursor)->page.id.page_no()
- Closed
-
MDEV-28174 InnoDB: Assertion failure
- Closed
-
MDEV-28349 Provide "crash safe" options for CHECK TABLE and ALTER TABLE ... CHECK PARTITION ...
- Open
-
MDEV-29276 [FATAL] InnoDB: Page old data size 7898 new data size 7922, page old max ins size 8288 new max ins size 8264
- Closed
-
MDEV-30397 InnoDB crash due to DB_FAIL reported for a corrupted page
- Closed
-
MDEV-31245 Assertion Failure results in crash
- Closed
-
MDEV-31767 InnoDB tables are being flagged as corrupted on an I/O bound server
- Closed
-
MDEV-32044 Mariadb crash after upgrading to 11.0.3: Failing assertion: local_len >= BTR_EXTERN_FIELD_REF_SIZE
- Closed
-
MDEV-34233 InnoDB crashes due to corrupted ibdata1 (Assertion failure in innodb.undo_page)
- Open
-
MDEV-34773 Troubles with DB
- Closed
- links to