Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2.21, 10.3.17
-
None
Description
When importing a tablespace, especially when just having the .ibd tablespace file but no .cfg file, the import may fail with messages like:
2019-10-14 15:35:43 250 [Note] InnoDB: Phase I - Update all pages
|
2019-10-14 15:35:44 250 [Note] InnoDB: Sync to disk
|
2019-10-14 15:35:44 250 [Note] InnoDB: Sync to disk - done!
|
2019-10-14 15:35:44 250 [Note] InnoDB: Phase II - Purge records from index `Index_name`
|
2019-10-14 15:35:44 250 [ERROR] [FATAL] InnoDB: Trying to read page number 65200640 in space 574155, space name db/table, which is outside the tablespace bounds. Byte offset 0, len 16384
|
191014 15:35:44 [ERROR] mysqld got signal 6 ;
|
In such cases the import should simply be aborted, and the table left in DISCARD state.
Crashing the table due to a failed import doesn't look like a good idea as it is clear that the detected corruption is local to the not yet successfully imported table only
Attachments
Issue Links
- duplicates
-
MDEV-14342 Importing partial backup from XtraBackup can sometimes crash server
- Closed
- is blocked by
-
MDEV-21513 Fix some crashes in ALTER TABLE…IMPORT TABLESPACE
- Closed
- relates to
-
MDEV-13542 Crashing on a corrupted page is unhelpful
- Closed
-
MDEV-20974 Don't require .cfg files to import InnoDB tablespaces
- Closed