Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.1(EOL)
-
None
Description
Note: See also MDEV-13105.
10.1 58f87a41bd |
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Highest supported file format is Barracuda.
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: The log sequence number 1622838 in ibdata file do not match the log sequence number 1626705 in the ib_logfiles!
|
InnoDB: Error: Current page size 16384 != page size on page 4096
|
2017-06-16 20:15:25 139685753401472 [ERROR] InnoDB: innodb-page-size mismatch in tablespace ./test/t1.ibd (table test/t1)
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size:1024 Pages to analyze:64
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size: 1024, Possible space_id count:0
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size:2048 Pages to analyze:48
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size: 2048, Possible space_id count:0
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size:4096 Pages to analyze:24
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size: 4096, Possible space_id count:0
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size:8192 Pages to analyze:12
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size: 8192, Possible space_id count:0
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size:16384 Pages to analyze:6
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: VALID: space:4 page_no:0 page_size:16384
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: VALID: space:4 page_no:1 page_size:16384
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: VALID: space:4 page_no:2 page_size:16384
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: VALID: space:4 page_no:3 page_size:16384
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Page size: 16384, Possible space_id count:1
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: space_id:4, Number of pages matched: 4/4 (16384)
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Chosen space:4
|
|
2017-06-16 20:15:25 139685753401472 [Note] InnoDB: Restoring page 0 of tablespace 4
|
2017-06-16 20:15:25 139685753401472 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 4
|
2017-06-16 20:15:25 7f0b1fb63080 InnoDB: Operating system error number 2 in a file operation.
|
InnoDB: The error means the system cannot find the path specified.
|
InnoDB: If you are installing InnoDB, remember that you must create
|
InnoDB: directories yourself, InnoDB does not create them.
|
InnoDB: Error: could not open single-table tablespace file ./test/t1.ibd
|
InnoDB: We do not continue the crash recovery, because the table may become
|
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
|
InnoDB: To fix the problem and start mysqld:
|
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
|
InnoDB: open the file, you should modify the permissions.
|
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
|
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
|
InnoDB: crash recovery and ignore that table.
|
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
|
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
|
InnoDB: and force InnoDB to continue crash recovery here.
|
170616 20:15:25 [ERROR] mysqld got signal 6 ;
|
#4 0x00007f0b1d7e03fa in abort () from /lib/x86_64-linux-gnu/libc.so.6
|
#5 0x000055a145567860 in fil_load_single_table_tablespace (dbname=0x7ffe592a15e0 "test", filename=0x7ffe592a25b0 "t1.ibd") at /data/src/10.1/storage/xtradb/fil/fil0fil.cc:5100
|
#6 0x000055a145568211 in fil_load_single_table_tablespaces (pred=0x0) at /data/src/10.1/storage/xtradb/fil/fil0fil.cc:5469
|
#7 0x000055a14537b51b in recv_init_crash_recovery () at /data/src/10.1/storage/xtradb/log/log0recv.cc:2999
|
#8 0x000055a14537bc95 in recv_recovery_from_checkpoint_start_func (type=78656949, limit_lsn=18446744073709551615, flushed_lsn=1622838) at /data/src/10.1/storage/xtradb/log/log0recv.cc:3286
|
#9 0x000055a14545dce9 in innobase_start_or_create_for_mysql () at /data/src/10.1/storage/xtradb/srv/srv0start.cc:2615
|
#10 0x000055a1452ef0f4 in innobase_init (p=0x7f0b1cc36a70) at /data/src/10.1/storage/xtradb/handler/ha_innodb.cc:4437
|
#11 0x000055a144fbd335 in ha_initialize_handlerton (plugin=0x7f0b1cf24880) at /data/src/10.1/sql/handler.cc:513
|
#12 0x000055a144d99d69 in plugin_initialize (tmp_root=0x7ffe592a7d60, plugin=0x7f0b1cf24880, argc=0x55a146015770 <remaining_argc>, argv=0x7f0b1cc33438, options_only=false) at /data/src/10.1/sql/sql_plugin.cc:1400
|
#13 0x000055a144d9a952 in plugin_init (argc=0x55a146015770 <remaining_argc>, argv=0x7f0b1cc33438, flags=2) at /data/src/10.1/sql/sql_plugin.cc:1678
|
#14 0x000055a144cb9c45 in init_server_components () at /data/src/10.1/sql/mysqld.cc:5149
|
#15 0x000055a144cbacb0 in mysqld_main (argc=7, argv=0x7f0b1cc33438) at /data/src/10.1/sql/mysqld.cc:5736
|
#16 0x000055a144cb0400 in main (argc=6, argv=0x7ffe592a8af8) at /data/src/10.1/sql/main.cc:25
|
To reproduce:
on 10.1.20 clean server started with all defaults |
SET GLOBAL innodb_file_format = Barracuda; |
CREATE TABLE `t1` (`i` INT, `pk` BIGINT AUTO_INCREMENT PRIMARY KEY) |
ENGINE=InnoDB ROW_FORMAT=DYNAMIC PAGE_COMPRESSED=1 PAGE_COMPRESSION_LEVEL=9; |
SIGKILL the server.
Then start the current 10.1 server on the same folder, observe the crash.
Alternatively, you can download the datadir as described above from here: ftp://ftp.askmonty.org/public/mdev13113_data.tar.gz and just start the current 10.1 on it.
Attachments
Issue Links
- relates to
-
MDEV-13105 InnoDB fails to load a table with PAGE_COMPRESSION_LEVEL after upgrade from 10.1.20
- Closed