Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
Description
2017-06-16 1:51:01 140690340212800 [Note] InnoDB: Completed initialization of buffer pool
|
2017-06-16 1:51:01 140689607849728 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
|
2017-06-16 1:51:01 140690340212800 [Note] InnoDB: Highest supported file format is Barracuda.
|
2017-06-16 1:51:01 140690340212800 [Note] InnoDB: Upgrading redo log: 2*3072 pages; LSN=1769605
|
2017-06-16 1:51:01 140690340212800 [Note] InnoDB: Starting to delete and rewrite log files.
|
2017-06-16 1:51:01 140690340212800 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
|
2017-06-16 1:51:02 140690340212800 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
|
2017-06-16 1:51:03 140690340212800 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
|
2017-06-16 1:51:03 140690340212800 [Note] InnoDB: New log files created, LSN=1769605
|
2017-06-16 1:51:03 140690340212800 [ERROR] InnoDB: Data file './test/t1.ibd' uses page size 65536, but the innodb_page_size start-up parameter is 16384
|
2017-06-16 1:51:03 140690340212800 [ERROR] InnoDB: Operating system error number 2 in a file operation.
|
2017-06-16 1:51:03 140690340212800 [ERROR] InnoDB: The error means the system cannot find the path specified.
|
2017-06-16 1:51:03 140690340212800 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
|
2017-06-16 1:51:03 140690340212800 [ERROR] InnoDB: Could not find a valid tablespace file for `test/t1`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
|
2017-06-16 1:51:03 140690340212800 [Warning] InnoDB: Ignoring tablespace for `test`.`t1` because it could not be opened.
|
2017-06-16 1:51:03 140690340212800 [Note] InnoDB: 128 out of 128 rollback segments are active.
|
2017-06-16 1:51:03 140690340212800 [Note] InnoDB: Creating sys_virtual system tables.
|
To reproduce:
on 10.1.20 clean server started with all defaults |
MariaDB [test]> SET GLOBAL innodb_file_format = Barracuda; |
Query OK, 0 rows affected (0.00 sec) |
|
MariaDB [test]> CREATE TABLE `t1` (`pk` BIGINT AUTO_INCREMENT PRIMARY KEY, `i` INT) ENGINE=InnoDB ROW_FORMAT=DYNAMIC PAGE_COMPRESSED=1 PAGE_COMPRESSION_LEVEL=3; |
Query OK, 0 rows affected (0.67 sec) |
|
MariaDB [test]> INSERT INTO t1 VALUES (NULL,1); |
Query OK, 1 row affected (0.05 sec)
|
|
MariaDB [test]> shutdown;
|
Query OK, 0 rows affected (0.00 sec) |
Then start 10.2 on the same datadir, observe errors in the error log and
on 10.2 |
MariaDB [test]> check table t1; |
+---------+-------+----------+-------------------------------------------+ |
| Table | Op | Msg_type | Msg_text | |
+---------+-------+----------+-------------------------------------------+ |
| test.t1 | check | Warning | Tablespace is missing for table 'test/t1' | |
| test.t1 | check | Error | Table 'test.t1' doesn't exist in engine | |
| test.t1 | check | status | Operation failed | |
+---------+-------+----------+-------------------------------------------+ |
3 rows in set (0.00 sec) |
If you don't want to install 10.1.20, you can download the datadir prepared as described above from here:
ftp://ftp.askmonty.org/public/mdev13105_datadir.tar.gz
and start 10.2 on it.
Attachments
Issue Links
- relates to
-
MDEV-11623 MariaDB 10.1 fails to start datadir created with MariaDB 10.0/MySQL 5.6 using innodb-page-size!=16K
- Closed
-
MDEV-13113 Server crashes in fil_load_single_table_tablespace after crash-upgrade from 10.1.20
- Closed