[MDEV-18201] InnoDB: Operating system error number 2 in a file operation and InnoDB: Cannot open datafile for read-only upon startup on datadir restored from full backup - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2(EOL), 10.3(EOL), 10.4(EOL)
Fix Version/s: 10.4.2, 10.2.22, 10.3.13
Component/s: mariabackup, Storage Engine - InnoDB
Labels:
None

Description

10.4 30da40bb8c303
2019-01-10 16:07:43 0 [Note] InnoDB: New log files created, LSN=9813228
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.

Further attempts to open tables cause more errors

MariaDB [(none)]> show create table test.seq9;

ERROR 1932 (42S02): Table 'test.seq9' doesn't exist in engine

MariaDB [(none)]> show create table test.seq8;

ERROR 1932 (42S02): Table 'test.seq8' doesn't exist in engine

2019-01-10 16:16:17 9 [ERROR] InnoDB: Failed to find tablespace for table `test`.`seq9` in the cache. Attempting to load the tablespace with space id 649

2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.

2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.

2019-01-10 16:16:17 9 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71

2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.

2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.

2019-01-10 16:16:17 9 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.

2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd

2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd

2019-01-10 16:16:20 9 [ERROR] InnoDB: Table `test`.`seq8` is corrupted. Please drop the table and recreate.

The backup datadir before prepare is attached, as well as the backup log.
To reproduce, run

bin/mariabackup --prepare --target-dir=`pwd`/backup_before_prepare

bin/mariabackup --copy-back --target-dir=`pwd`/backup_before_prepare --datadir=`pwd`/data

and start the server. All defaults will do, or for the accuracy you can use --innodb-compression-algorithm=none which the initial server was run with. It doesn't make any difference.

I have no information yet whether it affects earlier versions.

Notes on the origin of the report

Please note it's not necessarily reproducible this way.

https://travis-ci.org/elenst/travis-tests/jobs/477530220

Tests: elenst-dev 0ebbe452
Toolbox: ece65ed3b78

perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547092682 --reporters=Backtrace,ErrorLog,Deadlock --skip-gendata --gendata-advanced --views --grammar=conf/mariadb/generic-dml.yy --redefine=conf/mariadb/bulk_insert.yy --mysqld=--log_output=FILE --mysqld=--max-statement-time=20 --mysqld=--lock-wait-timeout=10 --mysqld=--loose-innodb-lock-wait-timeout=5 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --filter=/home/travis/mariadb-toolbox/travis/10.4-combo-filter.ff --mysqld=--innodb-compression-algorithm=none --innodb-page-size=8K --engine=InnoDB --scenario=MariaBackupFull --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/modules/admin.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy

The test log is attached as trial.log

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

trial.log
60 kB
2019-01-10 14:27
backup_before_prepare.tar.gz
841 kB
2019-01-10 14:28
mbackup_backup.log
51 kB
2019-01-10 14:28
mysql.err
4 kB
2019-01-10 14:28

Issue Links

relates to

MDEV-18185 MariaBackup --prepare fails with InnoDB: Failing assertion: 0 in rename_table_in_prepare

Closed

Activity

Ascending order - Click to sort in descending order

Elena Stepanova created issue - 2019-01-10 14:28

Elena Stepanova made changes - 2019-01-10 14:29

Field	Original Value	New Value
Description	{noformat:title=10.4 30da40bb8c303} 2019-01-10 16:07:43 0 [Note] InnoDB: New log files created, LSN=9813228 2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-01-10 16:07:43 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71 2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-01-10 16:07:43 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue. {noformat} Further attempts to open tables cause more errors {code:sql} MariaDB [(none)]> show create table test.seq9; ERROR 1932 (42S02): Table 'test.seq9' doesn't exist in engine MariaDB [(none)]> show create table test.seq8; ERROR 1932 (42S02): Table 'test.seq8' doesn't exist in engine {code} {noformat} 2019-01-10 16:16:17 9 [ERROR] InnoDB: Failed to find tablespace for table `test`.`seq9` in the cache. Attempting to load the tablespace with space id 649 2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:16:17 9 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71 2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:16:17 9 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd 2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd 2019-01-10 16:16:20 9 [ERROR] InnoDB: Table `test`.`seq8` is corrupted. Please drop the table and recreate. {noformat} The backup datadir before {{prepare}} is attached, as well as the backup log. To reproduce, run {noformat} bin/mariabackup --prepare --target-dir=`pwd`/backup_before_prepare bin/mariabackup --copy-back --target-dir=`pwd`/backup_before_prepare --datadir=`pwd`/data {noformat} and start the server. All defaults will do, or for the accuracy you can use {{--innodb-compression-algorithm=none}} which the initial server was run with. It doesn't make any difference. ---- Notes on the origin of the report. Please note it's not necessarily reproducible this way. https://travis-ci.org/elenst/travis-tests/jobs/477530220 Tests: elenst-dev 0ebbe452 Toolbox: ece65ed3b78 {noformat} perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547092682 --reporters=Backtrace,ErrorLog,Deadlock --skip-gendata --gendata-advanced --views --grammar=conf/mariadb/generic-dml.yy --redefine=conf/mariadb/bulk_insert.yy --mysqld=--log_output=FILE --mysqld=--max-statement-time=20 --mysqld=--lock-wait-timeout=10 --mysqld=--loose-innodb-lock-wait-timeout=5 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --filter=/home/travis/mariadb-toolbox/travis/10.4-combo-filter.ff --mysqld=--innodb-compression-algorithm=none --innodb-page-size=8K --engine=InnoDB --scenario=MariaBackupFull --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/modules/admin.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy {noformat} The test log is attached as [^trial.log]	{noformat:title=10.4 30da40bb8c303} 2019-01-10 16:07:43 0 [Note] InnoDB: New log files created, LSN=9813228 2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-01-10 16:07:43 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71 2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-01-10 16:07:43 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue. {noformat} Further attempts to open tables cause more errors {code:sql} MariaDB [(none)]> show create table test.seq9; ERROR 1932 (42S02): Table 'test.seq9' doesn't exist in engine MariaDB [(none)]> show create table test.seq8; ERROR 1932 (42S02): Table 'test.seq8' doesn't exist in engine {code} {noformat} 2019-01-10 16:16:17 9 [ERROR] InnoDB: Failed to find tablespace for table `test`.`seq9` in the cache. Attempting to load the tablespace with space id 649 2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:16:17 9 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71 2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-01-10 16:16:17 9 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd 2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd 2019-01-10 16:16:20 9 [ERROR] InnoDB: Table `test`.`seq8` is corrupted. Please drop the table and recreate. {noformat} The backup datadir before {{prepare}} is attached, as well as the backup log. To reproduce, run {noformat} bin/mariabackup --prepare --target-dir=`pwd`/backup_before_prepare bin/mariabackup --copy-back --target-dir=`pwd`/backup_before_prepare --datadir=`pwd`/data {noformat} and start the server. All defaults will do, or for the accuracy you can use {{--innodb-compression-algorithm=none}} which the initial server was run with. It doesn't make any difference. ---- {color:gray} Notes on the origin of the report. Please note it's not necessarily reproducible this way. https://travis-ci.org/elenst/travis-tests/jobs/477530220 Tests: elenst-dev 0ebbe452 Toolbox: ece65ed3b78 {noformat} perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547092682 --reporters=Backtrace,ErrorLog,Deadlock --skip-gendata --gendata-advanced --views --grammar=conf/mariadb/generic-dml.yy --redefine=conf/mariadb/bulk_insert.yy --mysqld=--log_output=FILE --mysqld=--max-statement-time=20 --mysqld=--lock-wait-timeout=10 --mysqld=--loose-innodb-lock-wait-timeout=5 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --filter=/home/travis/mariadb-toolbox/travis/10.4-combo-filter.ff --mysqld=--innodb-compression-algorithm=none --innodb-page-size=8K --engine=InnoDB --scenario=MariaBackupFull --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/modules/admin.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy {noformat} The test log is attached as [^trial.log] {color}

Elena Stepanova made changes - 2019-01-10 14:33

Description

{noformat:title=10.4 30da40bb8c303}
2019-01-10 16:07:43 0 [Note] InnoDB: New log files created, LSN=9813228
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
{noformat}

Further attempts to open tables cause more errors
{code:sql}
MariaDB [(none)]> show create table test.seq9;
ERROR 1932 (42S02): Table 'test.seq9' doesn't exist in engine
MariaDB [(none)]> show create table test.seq8;
ERROR 1932 (42S02): Table 'test.seq8' doesn't exist in engine
{code}
{noformat}
2019-01-10 16:16:17 9 [ERROR] InnoDB: Failed to find tablespace for table `test`.`seq9` in the cache. Attempting to load the tablespace with space id 649
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Table `test`.`seq8` is corrupted. Please drop the table and recreate.
{noformat}

The backup datadir before {{prepare}} is attached, as well as the backup log.
To reproduce, run
{noformat}
bin/mariabackup --prepare --target-dir=`pwd`/backup_before_prepare
bin/mariabackup --copy-back --target-dir=`pwd`/backup_before_prepare --datadir=`pwd`/data
{noformat}
and start the server. All defaults will do, or for the accuracy you can use {{--innodb-compression-algorithm=none}} which the initial server was run with. It doesn't make any difference.

----
{color:gray}
Notes on the origin of the report. *Please note it's not necessarily reproducible this way.*

https://travis-ci.org/elenst/travis-tests/jobs/477530220

Tests: elenst-dev 0ebbe452
Toolbox: ece65ed3b78
{noformat}
perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547092682 --reporters=Backtrace,ErrorLog,Deadlock --skip-gendata --gendata-advanced --views --grammar=conf/mariadb/generic-dml.yy --redefine=conf/mariadb/bulk_insert.yy --mysqld=--log_output=FILE --mysqld=--max-statement-time=20 --mysqld=--lock-wait-timeout=10 --mysqld=--loose-innodb-lock-wait-timeout=5 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --filter=/home/travis/mariadb-toolbox/travis/10.4-combo-filter.ff --mysqld=--innodb-compression-algorithm=none --innodb-page-size=8K --engine=InnoDB --scenario=MariaBackupFull --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/modules/admin.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy
{noformat}
The test log is attached as [^trial.log]
{color}

{noformat:title=10.4 30da40bb8c303}
2019-01-10 16:07:43 0 [Note] InnoDB: New log files created, LSN=9813228
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
{noformat}

Further attempts to open tables cause more errors
{code:sql}
MariaDB [(none)]> show create table test.seq9;
ERROR 1932 (42S02): Table 'test.seq9' doesn't exist in engine
MariaDB [(none)]> show create table test.seq8;
ERROR 1932 (42S02): Table 'test.seq8' doesn't exist in engine
{code}
{noformat}
2019-01-10 16:16:17 9 [ERROR] InnoDB: Failed to find tablespace for table `test`.`seq9` in the cache. Attempting to load the tablespace with space id 649
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Table `test`.`seq8` is corrupted. Please drop the table and recreate.
{noformat}

The backup datadir before {{prepare}} is attached, as well as the backup log.
To reproduce, run
{noformat}
bin/mariabackup --prepare --target-dir=`pwd`/backup_before_prepare
bin/mariabackup --copy-back --target-dir=`pwd`/backup_before_prepare --datadir=`pwd`/data
{noformat}
and start the server. All defaults will do, or for the accuracy you can use {{--innodb-compression-algorithm=none}} which the initial server was run with. It doesn't make any difference.

----
{panel:title=Notes on the origin of the report|bgColor=#EEEEEE}
{color:#999999}
*Please note it's not necessarily reproducible this way.*

https://travis-ci.org/elenst/travis-tests/jobs/477530220

Tests: elenst-dev 0ebbe452
Toolbox: ece65ed3b78
{noformat}
perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547092682 --reporters=Backtrace,ErrorLog,Deadlock --skip-gendata --gendata-advanced --views --grammar=conf/mariadb/generic-dml.yy --redefine=conf/mariadb/bulk_insert.yy --mysqld=--log_output=FILE --mysqld=--max-statement-time=20 --mysqld=--lock-wait-timeout=10 --mysqld=--loose-innodb-lock-wait-timeout=5 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --filter=/home/travis/mariadb-toolbox/travis/10.4-combo-filter.ff --mysqld=--innodb-compression-algorithm=none --innodb-page-size=8K --engine=InnoDB --scenario=MariaBackupFull --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/modules/admin.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy
{noformat}
The test log is attached as [^trial.log]
{color}
{panel}

Elena Stepanova made changes - 2019-01-10 14:34

Assignee

Elena Stepanova [ elenst ]

Vladislav Vaintroub [ wlad ]

Elena Stepanova made changes - 2019-01-10 14:37

Description

{noformat:title=10.4 30da40bb8c303}
2019-01-10 16:07:43 0 [Note] InnoDB: New log files created, LSN=9813228
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
{noformat}

Further attempts to open tables cause more errors
{code:sql}
MariaDB [(none)]> show create table test.seq9;
ERROR 1932 (42S02): Table 'test.seq9' doesn't exist in engine
MariaDB [(none)]> show create table test.seq8;
ERROR 1932 (42S02): Table 'test.seq8' doesn't exist in engine
{code}
{noformat}
2019-01-10 16:16:17 9 [ERROR] InnoDB: Failed to find tablespace for table `test`.`seq9` in the cache. Attempting to load the tablespace with space id 649
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Table `test`.`seq8` is corrupted. Please drop the table and recreate.
{noformat}

The backup datadir before {{prepare}} is attached, as well as the backup log.
To reproduce, run
{noformat}
bin/mariabackup --prepare --target-dir=`pwd`/backup_before_prepare
bin/mariabackup --copy-back --target-dir=`pwd`/backup_before_prepare --datadir=`pwd`/data
{noformat}
and start the server. All defaults will do, or for the accuracy you can use {{--innodb-compression-algorithm=none}} which the initial server was run with. It doesn't make any difference.

----
{panel:title=Notes on the origin of the report|bgColor=#EEEEEE}
{color:#999999}
*Please note it's not necessarily reproducible this way.*

https://travis-ci.org/elenst/travis-tests/jobs/477530220

Tests: elenst-dev 0ebbe452
Toolbox: ece65ed3b78
{noformat}
perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547092682 --reporters=Backtrace,ErrorLog,Deadlock --skip-gendata --gendata-advanced --views --grammar=conf/mariadb/generic-dml.yy --redefine=conf/mariadb/bulk_insert.yy --mysqld=--log_output=FILE --mysqld=--max-statement-time=20 --mysqld=--lock-wait-timeout=10 --mysqld=--loose-innodb-lock-wait-timeout=5 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --filter=/home/travis/mariadb-toolbox/travis/10.4-combo-filter.ff --mysqld=--innodb-compression-algorithm=none --innodb-page-size=8K --engine=InnoDB --scenario=MariaBackupFull --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/modules/admin.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy
{noformat}
The test log is attached as [^trial.log]
{color}
{panel}

{noformat:title=10.4 30da40bb8c303}
2019-01-10 16:07:43 0 [Note] InnoDB: New log files created, LSN=9813228
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:07:43 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:07:43 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:07:43 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-10 16:07:43 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
{noformat}

Further attempts to open tables cause more errors
{code:sql}
MariaDB [(none)]> show create table test.seq9;
ERROR 1932 (42S02): Table 'test.seq9' doesn't exist in engine
MariaDB [(none)]> show create table test.seq8;
ERROR 1932 (42S02): Table 'test.seq8' doesn't exist in engine
{code}
{noformat}
2019-01-10 16:16:17 9 [ERROR] InnoDB: Failed to find tablespace for table `test`.`seq9` in the cache. Attempting to load the tablespace with space id 649
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Cannot open datafile for read-only: './test/seq9.ibd' OS error: 71
2019-01-10 16:16:17 9 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-10 16:16:17 9 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-10 16:16:17 9 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`seq9``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Expected tablespace id 631 but found 649 in the file ./test/seq8.ibd
2019-01-10 16:16:20 9 [ERROR] InnoDB: Table `test`.`seq8` is corrupted. Please drop the table and recreate.
{noformat}

The backup datadir before {{prepare}} is attached, as well as the backup log.
To reproduce, run
{noformat}
bin/mariabackup --prepare --target-dir=`pwd`/backup_before_prepare
bin/mariabackup --copy-back --target-dir=`pwd`/backup_before_prepare --datadir=`pwd`/data
{noformat}
and start the server. All defaults will do, or for the accuracy you can use {{--innodb-compression-algorithm=none}} which the initial server was run with. It doesn't make any difference.

*I have no information yet whether it affects earlier versions*.

----
{panel:title=Notes on the origin of the report|bgColor=#EEEEEE}
{color:#999999}
*Please note it's not necessarily reproducible this way.*

https://travis-ci.org/elenst/travis-tests/jobs/477530220

Tests: elenst-dev 0ebbe452
Toolbox: ece65ed3b78
{noformat}
perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547092682 --reporters=Backtrace,ErrorLog,Deadlock --skip-gendata --gendata-advanced --views --grammar=conf/mariadb/generic-dml.yy --redefine=conf/mariadb/bulk_insert.yy --mysqld=--log_output=FILE --mysqld=--max-statement-time=20 --mysqld=--lock-wait-timeout=10 --mysqld=--loose-innodb-lock-wait-timeout=5 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --filter=/home/travis/mariadb-toolbox/travis/10.4-combo-filter.ff --mysqld=--innodb-compression-algorithm=none --innodb-page-size=8K --engine=InnoDB --scenario=MariaBackupFull --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/modules/admin.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy
{noformat}
The test log is attached as [^trial.log]
{color}
{panel}

Vladislav Vaintroub made changes - 2019-01-10 18:49

Status

Open [ 1 ]

Confirmed [ 10101 ]

Vladislav Vaintroub made changes - 2019-01-10 18:49

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Vladislav Vaintroub made changes - 2019-01-10 18:50

Fix Version/s		10.4.2 [ 23229 ]
Fix Version/s		10.3.13 [ 23215 ]
Fix Version/s		10.2.22 [ 23250 ]
Fix Version/s	10.4 [ 22408 ]
Resolution		Fixed [ 1 ]
Status	In Progress [ 3 ]	Closed [ 6 ]

Vladislav Vaintroub made changes - 2019-01-10 18:50

Affects Version/s		10.2 [ 14601 ]
Affects Version/s		10.3 [ 22126 ]

Vladislav Vaintroub made changes - 2019-01-10 18:51

Link

This issue relates to ~~MDEV-18185~~ [ ~~MDEV-18185~~ ]

Sergei Golubchik made changes - 2021-12-06 21:48

Workflow

MariaDB v3 [ 91625 ]

MariaDB v4 [ 155488 ]

People

Assignee:: Vladislav Vaintroub

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2019-01-10 14:28

Updated:: 2019-01-10 18:51

Resolved:: 2019-01-10 18:50

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates

Git Integration