Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.1.24
-
None
Description
Currently mariabackup doesn't work properly with custom innodb_page_size
$ for k in 4k 8k 32k 64k; do ./mtr --mysqld=--innodb-buffer-pool-size=28M --mysqld=--innodb-page-size=$k --mem --parallel=auto --suite=mariabackup --force; done | grep -E '\[ fail \]|--mysqld'
|
Logging: 10.1/mysql-test/mysql-test-run.pl --mysqld=--innodb-buffer-pool-size=28M --mysqld=--innodb-page-size=4k --mem --parallel=auto --suite=mariabackup --force
|
mariabackup.xb_fulltext_encrypted w3 [ fail ]
|
mariabackup.xb_file_key_management w7 [ fail ]
|
mariabackup.full_backup w5 [ fail ]
|
mariabackup.partition_data_external w3 [ fail ]
|
mariabackup.incremental_backup w8 [ fail ]
|
mariabackup.incremental_encrypted w6 [ fail ]
|
mariabackup.xb_partition w4 [ fail ]
|
mariabackup.partial w2 [ fail ]
|
mariabackup.xb_compressed_encrypted w1 [ fail ]
|
mariabackup.xbstream w5 [ fail ]
|
mysql-test-run: *** ERROR: there were failing test cases
|
Logging: 10.1/mysql-test/mysql-test-run.pl --mysqld=--innodb-buffer-pool-size=28M --mysqld=--innodb-page-size=8k --mem --parallel=auto --suite=mariabackup --force
|
mariabackup.xb_partition w1 [ fail ]
|
mariabackup.partition_data_external w1 [ fail ]
|
...
|
the suite could not be run for 32k and 64k page size, because that would require bigger --innodb-log-file-size , which is blocked by MDEV-12709 "mariabackup mtr tests don't handle properly option --mysqld='--innodb..."
typical errors:
InnoDB: Unable to open undo tablespace './undo30579'.
xtrabackup: innodb_init(): Error occured.
...
InnoDB: Error: Current page size 8192 != page size on page 16384
InnoDB: innodb-page-size mismatch in tablespace ./test/p#P#p5.ibd (table test/p#P#p5)
2017-06-01 08:54:43 7f4cdeba4bc0 InnoDB: Operating system error number 2 in a file operation.
...
Attachments
Issue Links
- is blocked by
-
-
- Closed
-
- relates to
-
-
- Closed
-