[MDEV-12122] Error "Log sequence number at the start XXX and the end 0 do not match" for PAGE_COMPRESSED tables Created: 2017-02-24  Updated: 2017-07-31  Resolved: 2017-07-31

Status: Closed
Project: MariaDB Server
Component/s: Backup
Affects Version/s: 10.1.22
Fix Version/s: 10.1.23

Type: Bug Priority: Major
Reporter: Andrii Nikitin (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Attachments: File mtr.log    

 Description   

Tables with page compression may show errors during backup:

xtrabackup: Generating a list of tablespaces
170224 09:38:15 [01] Copying ./ibdata1 to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/ibdata1
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Page 65 is a doublewrite buffer page, skipping.
InnoDB: Log sequence number at the start 1619866 and the end 0 do not match.
[01] xtrabackup: Page 74 is a doublewrite buffer page, skipping.
InnoDB: Log sequence number at the start 1621444 and the end 0 do not match.
[01] xtrabackup: Page 75 is a doublewrite buffer page, skipping.
170224 09:38:15 [01]        ...done
170224 09:38:15 [01] Copying ./mysql/innodb_table_stats.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/mysql/innodb_table_stats.ibd
170224 09:38:15 [01]        ...done
170224 09:38:15 [01] Copying ./mysql/innodb_index_stats.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/mysql/innodb_index_stats.ibd
170224 09:38:15 [01]        ...done
170224 09:38:15 [01] Copying ./mysql/gtid_slave_pos.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/mysql/gtid_slave_pos.ibd
170224 09:38:15 [01]        ...done
170224 09:38:15 [01] Copying ./test/t.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/test/t.ibd
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
170224 09:38:16 >> log scanned up to (1621451)
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Database page corruption detected at page 1, retrying...
InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
[01] xtrabackup: Error: failed to read page after 10 retries. File ./test/t.ibd seems to be corrupted.
[01] xtrabackup: Error: xtrabackup_copy_datafile() failed.

I can easily reproduce the problem by injecting "do sleep(5);" into xb_page_compress.test before --backup command



 Comments   
Comment by Jan Lindström (Inactive) [ 2017-02-24 ]

Yes, naturally they are not same as page compressed tables with innodb-use-trim=1 do not have LSN at the end of the page.

Comment by Andrii Nikitin (Inactive) [ 2017-07-28 ]

jplindst, I cannot reproduce the problem with mentioned test case in current 10.1 - do you have idea if this was really fixed? (and maybe when). I will just close it, unless somebody disagrees.

Comment by Jan Lindström (Inactive) [ 2017-07-31 ]

anikitin It has been fixed most likely in MDEV-11759: Encryption code in MariaDB 10.1/10.2 causes

Generated at Thu Feb 08 07:55:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.