Different behaviour with 2.3 and 2.4 if it can not read first page of tablespace
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Confirmed
|
Medium
|
Unassigned | ||
2.3 |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Description:
I have created a null folder under datadir and added some files there manually:
[shahriyar.
total 0
-rw-rw-r-- 1 shahriyar.rzaev shahriyar.rzaev 0 Apr 14 13:06 0x0.frm
-rw-rw-r-- 1 shahriyar.rzaev shahriyar.rzaev 0 Apr 14 13:06 0x0.ibd
-rw-rw-r-- 1 shahriyar.rzaev shahriyar.rzaev 0 Apr 14 12:51 db.opt
-rw-rw-r-- 1 shahriyar.rzaev shahriyar.rzaev 0 Apr 14 12:51 null.frm
-rw-rw-r-- 1 shahriyar.rzaev shahriyar.rzaev 0 Apr 14 12:51 null.ibd
Then tried to backup with 2.3:
/home/shahriyar
xtrabackup: Generating a list of tablespaces
InnoDB: Retry attempts for reading partial data failed.
InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 0.
2017-04-14 13:31:05 7ffff7fe0840 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation
2017-04-14 13:31:05 7ffff7fe0840 InnoDB: Assertion failure in thread 140737354008640 in file os0file.cc line 658
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
(gdb) bt
+bt
#0 0x00007ffff5ce15d7 in __GI_raise (sig=sig@entry=6) at ../nptl/
#1 0x00007ffff5ce2cc8 in __GI_abort () at abort.c:90
#2 0x0000000000808cb3 in os_file_
#3 0x0000000000808ce4 in os_file_
#4 0x000000000080a54a in os_file_read_func (file=12, buf=0x179c000, offset=0, n=16384) at /home/shahriyar
#5 0x00000000007eacec in fil_read_first_page (data_file=12, one_read_already=0, flags=0x7ffffff
#6 0x00000000007ee622 in fil_validate_
#7 0x00000000007eeb60 in fil_load_
#8 0x00000000007ef4b6 in fil_load_
#9 0x0000000000610e8c in xb_load_tablespaces () at /home/shahriyar
#10 0x0000000000612b7b in xtrabackup_
#11 0x00000000006198c1 in main (argc=8, argv=0x7fffffff
With 2.4:
InnoDB: Number of pools: 1
170414 13:25:32 >> log scanned up to (40981675)
xtrabackup: Generating a list of tablespaces
InnoDB: Cannot read first page of './null/0x0.ibd' I/O error
InnoDB: Cannot read first page in datafile: ./null/0x0.ibd, Space ID:184467440737
InnoDB: Cannot read first page of './null/null.ibd' I/O error
InnoDB: Cannot read first page in datafile: ./null/null.ibd, Space ID:184467440737
InnoDB: Allocated tablespace ID 1 for mysql/innodb_
InnoDB: Cannot read first page of './root_
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXB-787