[MDEV-14175] backup shows corruption for 5.5 Server with innodb-fast-checksum Created: 2017-10-27  Updated: 2017-11-06  Resolved: 2017-10-27

Status: Closed
Project: MariaDB Server
Component/s: Backup, Storage Engine - XtraDB
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Andrii Nikitin (Inactive) Assignee: Marko Mäkelä
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-14169 MariaDB 10.0/10.1 fail to start with ... Closed
relates to MDEV-14936 Test MariaDB Backup 10.1 against newe... Closed

 Description   

test innodb_fast_checksum.sh

Starting /home/a/env1/m4-5.5.58/../_depot/m-tar/5.5.58/bin/mysqld --defaults-file=/dev/shm/__var0/var1/my.cnf   
171027 13:42:34 [Note] /home/a/env1/m4-5.5.58/../_depot/m-tar/5.5.58/bin/mysqld (mysqld 5.5.58-MariaDB) starting as process 18291 ...
2017-10-27 13:42:35: bash: Made 1 attempts to connect to server
2017-10-27 13:42:36: bash: Made 2 attempts to connect to server
2017-10-27 13:42:36: bash: Server with id=1 has been started on port 30447, socket /dev/shm/__var0/tmp/mysql.sock.FzSieM
2017-10-27 13:42:36: bash: Loading sakila
2017-10-27 13:42:36: bash: Loading sakila scheme
2017-10-27 13:42:36: bash: Loading sakila data
2017-10-27 13:42:36: bash: ===> /home/a/env1/m7-10.1/bld/extra/mariabackup//mariabackup --innobackupex --defaults-file=/dev/shm/__var0/var1/my.cnf --no-version-check --no-timestamp /dev/shm/__var0/var1/backup
171027 13:42:36 innobackupex: Starting the backup operation
 
IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".
 
171027 13:42:36 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: /dev/shm/__var0/tmp/mysql.sock.FzSieM
Using server version 5.5.58-MariaDB
--innobackupex based on MariaDB server 10.1.29-MariaDB Linux (x86_64) 
mariabackup: uses posix_fadvise().
mariabackup: cd to /dev/shm/__var0/var1/data/
mariabackup: open files limit requested 0, set to 1024
mariabackup: using the following InnoDB configuration:
mariabackup:   innodb_data_home_dir = ./
mariabackup:   innodb_data_file_path = ibdata1:10M:autoextend
mariabackup:   innodb_log_group_home_dir = ./
mariabackup:   innodb_log_files_in_group = 2
mariabackup:   innodb_log_file_size = 50331648
171027 13:42:36 >> log scanned up to (8411847)
mariabackup: Generating a list of tablespaces
171027 13:42:37 [01] Copying ./ibdata1 to /dev/shm/__var0/var1/backup/ibdata1
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Database page corruption detected at page 0, retrying...
171027 13:42:37 >> log scanned up to (8411847)
[01] mariabackup: Database page corruption detected at page 0, retrying...
[01] mariabackup: Error: failed to read page after 10 retries. File ./ibdata1 seems to be corrupted.
[01] mariabackup: Error: xtrabackup_copy_datafile() failed.
[01] mariabackup: Error: failed to copy datafile.
2017-10-27 13:42:37: bash: ===> mariabackup failed with exit code 1
[innodb_fast_checksum] (4 sec) (res 1) FAIL



 Comments   
Comment by Marko Mäkelä [ 2017-10-27 ]

innodb_fast_shutdown is an XtraDB extension that appeared in MariaDB 5.1.47, 5.2.1, 5.5.20.
The option was deprecated in Percona XtraDB 5.5.28-29.2. One could claim that the idea was merged upstream, by MySQL 5.6’s introduction of innodb_checksum_algorithm.
Because Percona only supported this checksum in a few minor 5.5 releases before deprecating it, I do not think that we should spend time to reimplement and test this checksum algorithm in the MariaDB 10.x series.

Generated at Thu Feb 08 08:11:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.