Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.1.26, 10.0.32, 10.0(EOL), 10.1(EOL), 10.2(EOL)
-
Debian Jessie (MariaDB 10.0) / Debian Stretch (MariaDB 10.1)
-
10.1.29
Description
I'm trying to migrate from MariaDB 5.5 to 10.1 via 10.0 with innodb-page-size = 8192.
I first got this error when I migrated to 10.0.32 and only then came across the original bug report. Now I still get the same known error, despite having upgraded to 10.1.26 and the original error said to be fixed in 10.1.21:
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: innodb-page-size has been changed from the default value 16384 to 8192 .
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: Using mutexes to ref count buffer pool pages
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: The InnoDB memory heap is disabled
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: Compressed tables use zlib 1.2.8
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: Using Linux native AIO
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: Using SSE crc32 instructions
|
2017-10-27 11:35:23 139861476192832 [Note] InnoDB: Initializing buffer pool, size = 192.0G
|
2017-10-27 11:35:34 139861476192832 [Note] InnoDB: Completed initialization of buffer pool
|
InnoDB: Error: Current page size 8192 != page size on page 16384
|
2017-10-27 11:35:36 139861476192832 [Note] InnoDB: Restoring page 0 of tablespace 0
|
2017-10-27 11:35:36 139861476192832 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
|
2017-10-27 11:35:36 139861476192832 [ERROR] InnoDB: innodb-page-size mismatch in data file /db/data/ibdata1
|
2017-10-27 11:35:36 139861476192832 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
|
2017-10-27 11:35:36 139861476192832 [ERROR] Plugin 'InnoDB' init function returned error.
|
2017-10-27 11:35:36 139861476192832 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
|
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-