Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4(EOL)
-
None
Description
Note: Patches for MDEV-18201 and MDEV-18184 should already be in the tree, according to git history.
10.4 10.4 edba047080 |
2019-01-16 23:41:23 0 [Note] InnoDB: New log files created, LSN=37159799
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/#sql-5c90_11.ibd' OS error: 71
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
|
2019-01-16 23:41:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`#sql-5c90_11``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
|
...
|
Full error log is attached as mysql.err
The backup datadir before prepare can be found here:
ftp://ftp.askmonty.org/public/mdev18309-backup_before_prepare.tar.gz
The backup log is attached as mbackup_backup.log
To reproduce, unpack the backup datadir, adjust the path to the plugin dir and the encryption key file and 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 with
--innodb-encrypt-tables --innodb-encrypt-log --innodb-encryption-threads=4 --aria-encrypt-tables=1 --encrypt-tmp-disk-tables=1 --file-key-management --file-key-management-filename=/home/travis/mariadb-toolbox/data/keys.txt --plugin-load-add=file_key_management --innodb-compression-algorithm=zlib --innodb-page-size=8K
|
I have no information yet whether it affects earlier versions.
Please note it's not necessarily reproducible this way.
https://travis-ci.org/elenst/travis-tests/jobs/480418805
Tests: elenst-dev 23f517b6dba9c7b542e279d6ab9b1b24c578d6ab
Toolbox: c826c29aaabaf8bc9ba9363b7a9c6427ee9f5810
perl ./runall-new.pl --basedir=/home/travis/server --vardir=/home/travis/logs/vardir --duration=350 --threads=4 --seed=1547681839 --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-encrypt-tables --mysqld=--innodb-encrypt-log --mysqld=--innodb-encryption-threads=4 --mysqld=--aria-encrypt-tables=1 --mysqld=--encrypt-tmp-disk-tables=1 --mysqld=--file-key-management --mysqld=--file-key-management-filename=/home/travis/mariadb-toolbox/data/keys.txt --mysqld=--plugin-load-add=file_key_management --mysqld=--innodb-compression-algorithm=zlib --mysqld=--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
|
Test log is attached as trial.log
Attachments
Issue Links
- relates to
-
MDEV-18733 MariaDB slow start after crash recovery
-
- Closed
-
It is still reproducible for me on 10.4 17cbae65 (which is 2 commits before the latest one as of this moment) as described, with additional steps that I didn't mention specifically:
Please note that the server still starts. To see the described errors, you need to check the error log.
10.4 17cbae65
2019-04-02 2:07:49 0 [Note] InnoDB: innodb_page_size=8192
2019-04-02 2:07:49 0 [Note] InnoDB: Using Linux native AIO
2019-04-02 2:07:49 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2019-04-02 2:07:49 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-02 2:07:49 0 [Note] InnoDB: Uses event mutexes
2019-04-02 2:07:49 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-04-02 2:07:49 0 [Note] InnoDB: Number of pools: 1
2019-04-02 2:07:49 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-04-02 2:07:49 0 [Note] mysqld: O_TMPFILE is not supported on /data/bld/10.4/data/tmp (disabling future attempts)
2019-04-02 2:07:49 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-02 2:07:49 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-02 2:07:49 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-02 2:07:49 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
2019-04-02 2:07:49 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes
2019-04-02 2:07:49 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2019-04-02 2:07:49 0 [Note] InnoDB: New log files created, LSN=37159799
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/#sql-5c90_11.ibd' OS error: 71
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`#sql-5c90_11``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-04-02 2:07:49 0 [Warning] InnoDB: Ignoring tablespace for `test`.`#sql-5c90_11` because it could not be opened.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/#sql-5c90_e.ibd' OS error: 71
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`#sql-5c90_e``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-04-02 2:07:49 0 [Warning] InnoDB: Ignoring tablespace for `test`.`#sql-5c90_e` because it could not be opened.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/#sql-5c90_11.ibd' OS error: 71
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`#sql-5c90_11``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-04-02 2:07:49 0 [Note] InnoDB: Deleting ./test/#sql-5c90_11.ibd
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/#sql-5c90_e.ibd' OS error: 71
2019-04-02 2:07:49 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-04-02 2:07:49 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-04-02 2:07:49 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-04-02 2:07:49 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`#sql-5c90_e``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2019-04-02 2:07:49 0 [Note] InnoDB: Deleting ./test/#sql-5c90_e.ibd
2019-04-02 2:07:49 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-04-02 2:07:49 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-04-02 2:07:49 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-04-02 2:07:49 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-04-02 2:07:49 0 [Note] InnoDB: Waiting for purge to start
2019-04-02 2:07:49 0 [Note] InnoDB: 10.4.4 started; log sequence number 37159948; transaction id 3824
2019-04-02 2:07:49 0 [Note] InnoDB: Creating #1 encryption thread id 140026235041536 total threads 4.
2019-04-02 2:07:49 0 [Note] InnoDB: Creating #2 encryption thread id 140026226648832 total threads 4.
2019-04-02 2:07:49 0 [Note] InnoDB: Creating #3 encryption thread id 140026218256128 total threads 4.
2019-04-02 2:07:49 0 [Note] InnoDB: Loading buffer pool(s) from /data/bld/10.4/data/ib_buffer_pool
2019-04-02 2:07:49 0 [Note] InnoDB: Creating #4 encryption thread id 140025933068032 total threads 4.
2019-04-02 2:07:49 0 [Note] InnoDB: Buffer pool(s) load completed at 190402 2:07:49
2019-04-02 2:07:49 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-04-02 2:07:49 0 [Note] Server socket created on IP: '::'.
2019-04-02 2:07:49 0 [Note] Reading of all Master_info entries succeded
2019-04-02 2:07:49 0 [Note] Added new Master_info '' to hash table
2019-04-02 2:07:49 0 [Note] /data/bld/10.4/bin/mysqld: ready for connections.
Version: '10.4.4-MariaDB-debug' socket: '/data/bld/10.4/data/tmp/mysql.sock' port: 3306 Source distribution