Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
10.3.17, 10.3.21, 10.3.23
Description
It is observed that, while taking the backup using mariabackup(10.3.17) it's keep failing with following error:
Backup command used:
/var/lib/mysql/bin/mariabackup --defaults-file=/etc/my.cnf --user=**** --password=******* --backup --skip-encrypted-backup --compress --ftwrl-wait-timeout=5 --ftwrl-wait-threshold=300 --ftwrl-wait-query-type=all --target-dir=/tmp/backup/full_backup_2019
|
|
mariabackup output:
[00] 2019-11-16 06:29:24 Connecting to MySQL server host: localhost, user: xxx, password: xxx, port: 3306, socket: /var/lib/mysql/mysql.sock
|
[00] 2019-11-16 06:29:24 Using server version 10.3.17-MariaDB-log
|
/var/lib/mysql/bin/mariabackup based on MariaDB server 10.3.17-MariaDB Linux (x86_64)
|
....
|
....
|
[01] 2019-11-16 06:29:27 Compressing ./foo/bar.ibd to /tmp/backup/full_backup_2019/foo/bar.ibd.qp
|
[01] 2019-11-16 06:29:27 ...done
|
[01] 2019-11-16 06:29:27 Compressing ./foo/foobar.ibd to /tmp/backup/full_backup_2019/foo/foobar.ibd.qp
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:27 Database page corruption detected at page 5, retrying...
|
[01] 2019-11-16 06:29:28 Database page corruption detected at page 5, retrying...
|
[00] 2019-11-16 06:29:28 >> log scanned up to (30851334774)
|
[01] 2019-11-16 06:29:28 Error: failed to read page after 10 retries. File ./foo/foobar.ibd seems to be corrupted.
|
2019-11-16 6:29:28 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
|
.......
|
.......
|
InnoDB: End of page dump
|
2019-11-16 6:29:28 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 3454859770, calculated checksums for field1: crc32 3454859770, innodb 3654618756, page type 17855 == INDEX.none 3735928559, stored checksum in field2 3454859770, calculated checksums for field2: crc32 3454859770, innodb 4252287317, none 3735928559, page LSN 7 450897511, low 4 bytes of LSN at page end 450897511, page number (if stored to page already) 7, space id (if created with >= MySQL-4.1.1 and stored already) 1962
|
2019-11-16 6:29:28 0 [Note] InnoDB: Page may be an index page where index id is 5185
|
[01] 2019-11-16 06:29:28 mariabackup: xtrabackup_copy_datafile() failed.
|
[00] FATAL ERROR: 2019-11-16 06:29:28 failed to copy datafile.
|
|
Did tried, fixing the table (pointed as corrupted) with following, but the same issue is occurring.
set OLD_ALTER_TABLE=1
Alter table table_name engine=InnoDB
Alter table table_name FORCE
Take mysqldump of table and restore it to Database
Attachments
Issue Links
- is duplicated by
-
MDEV-24260 mariabackup and innochecksum detects page faults but all ok in application
- Closed
- relates to
-
MDEV-19871 Add page id matching check in innochecksum tool
- Closed
-
MDEV-22929 MariaBackup option to report and/or continue when corruption is encountered
- Closed
-
MDEV-23971 add the ability to fix corrupted pages on --prepare
- Closed
-
MDEV-29938 InnoDB: Assertion failure in btr0pcur.cc line 532
- Open
-
MDEV-25361 innochecksum must not report errors for freed pages
- Closed