[MDEV-12873] InnoDB SYS_TABLES.TYPE incompatibility for PAGE_COMPRESSED=YES in MariaDB 10.2.2 to 10.2.6 Created: 2017-05-23  Updated: 2021-10-20  Resolved: 2017-07-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.2, 10.2.3, 10.2.4, 10.2.5, 10.3.0, 10.2.6
Fix Version/s: 10.1.25, 10.2.7, 10.3.1

Type: Bug Priority: Blocker
Reporter: Denis Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None
Environment:

Windows Server 2012 R2

Issue Links:
Relates
relates to MDEV-13015 After restart, InnoDB wrongly thinks ... Closed
relates to MDEV-12309 Test migration from MySQL 5.7 with na... Stalled
relates to MDEV-22627 InnoDB: Failing assertion: dict_tf2_i... Closed

 Description   

Here's the information MariaDB logged on the crash, hope it helps

mysqld got exception 0xc0000005 ;
 
This could be because you hit a bug. It is also possible that this binary
 
or one of the libraries it was linked against is corrupt, improperly built,
 
or misconfigured. This error can also be caused by malfunctioning hardware.
 
 
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
 
 
We will try our best to scrape up some info that will hopefully help
 
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.
 
 
 
Server version: 10.2.6-MariaDB-log
 
key_buffer_size=209715200
 
read_buffer_size=2097152
 
max_used_connections=70
 
max_threads=2050
 
thread_count=77
 
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 254546 K  bytes of memory
 
Hope that's ok; if not, decrease some variables in the equation.
 
 
 
Thread pointer: 0x68ea3e7e58
 
Attempting backtrace. You can use the following information to find out
 
where mysqld died. If you see no messages after this, something went
 
terribly wrong...
 
mysqld.exe!std::_Tree<std::_Tset_traits<dict_foreign_t * __ptr64,dict_foreign_compare,ut_allocator<dict_foreign_t * __ptr64>,0> >::_Copy_nodes<std::_Tree<std::_Tset_traits<dict_foreign_t * __ptr64,dict_foreign_compare,ut_allocator<dict_foreign_t * __ptr64>,0> >::_Copy_tag>()[xtree:1962]
 
mysqld.exe!std::_Tree<std::_Tset_traits<dict_foreign_t * __ptr64,dict_foreign_compare,ut_allocator<dict_foreign_t * __ptr64>,0> >::_Copy<std::_Tree<std::_Tset_traits<dict_foreign_t * __ptr64,dict_foreign_compare,ut_allocator<dict_foreign_t * __ptr64>,0> >::_Copy_tag>()[xtree:1921]
 
mysqld.exe!std::_Tree<std::_Tset_traits<dict_foreign_t * __ptr64,dict_foreign_compare,ut_allocator<dict_foreign_t * __ptr64>,0> >::_Tree<std::_Tset_traits<dict_foreign_t * __ptr64,dict_foreign_compare,ut_allocator<dict_foreign_t * __ptr64>,0> ><std::_Wrap_alloc<ut_allocator<std::_Tree_node<dict_foreign_t * __ptr64,void * __ptr64> > > >()[xtree:1018]
 
mysqld.exe!dict_mem_table_free_foreign_vcol_set()[dict0mem.cc:927]
 
mysqld.exe!dict_mem_table_free()[dict0mem.cc:191]
 
mysqld.exe!i_s_sys_tables_fill_table()[i_s.cc:6155]
 
mysqld.exe!get_schema_tables_result()[sql_show.cc:8262]
 
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3434]
 
mysqld.exe!JOIN::exec()[sql_select.cc:3274]
 
mysqld.exe!mysql_select()[sql_select.cc:3668]
 
mysqld.exe!handle_select()[sql_select.cc:361]
 
mysqld.exe!execute_sqlcom_select()[sql_parse.cc:6431]
 
mysqld.exe!mysql_execute_command()[sql_parse.cc:3448]
 
mysqld.exe!mysql_parse()[sql_parse.cc:7879]
 
mysqld.exe!dispatch_command()[sql_parse.cc:1814]
 
mysqld.exe!do_command()[sql_parse.cc:1361]
 
mysqld.exe!do_handle_one_connection()[sql_connect.cc:1354]
 
mysqld.exe!handle_one_connection()[sql_connect.cc:1262]
 
mysqld.exe!pthread_start()[my_winthread.c:62]
 
mysqld.exe!thread_start<unsigned int (__cdecl*)(void * __ptr64)>()[thread.cpp:115]
 
KERNEL32.DLL!BaseThreadInitThunk()
 
ntdll.dll!RtlUserThreadStart()
 
 
 
Trying to get some variables.
 
Some pointers may be invalid and cause the dump to abort.
 
Query (0x68ea329030): SELECT * FROM `information_schema`.`INNODB_SYS_TABLES` LIMIT 500
 
Connection ID (thread ID): 158
 
Status: NOT_KILLED



 Comments   
Comment by Elena Stepanova [ 2017-05-23 ]

Did it happen after an upgrade from some other version, or is it a new instance?
Please paste or attach your cnf file(s), and also include the error log prior to the crash (at least from the last server start).
Thanks.

Comment by Denis [ 2017-05-23 ]

I've upgraded the instance from 10.1.23 to 10.2.6

Here's the log after the new version started working

2017-05-23  0:06:42 10284 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
 
2017-05-23  0:06:42 10284 [Warning] InnoDB: Using innodb_file_format_max is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
 
2017-05-23  0:06:42 10284 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-23  0:06:42 10284 [Note] InnoDB: Uses event mutexes
 
2017-05-23  0:06:42 10284 [Note] InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-23  0:06:42 10284 [Note] InnoDB: Number of pools: 1
 
2017-05-23  0:06:42 10284 [Note] InnoDB: Using generic crc32 instructions
 
2017-05-23  0:06:42 10284 [Note] InnoDB: Initializing buffer pool, total size = 20G, instances = 8, chunk size = 128M
 
2017-05-23  0:06:43 10284 [Note] InnoDB: Completed initialization of buffer pool
 
2017-05-23  0:06:44 10284 [Note] InnoDB: Highest supported file format is Barracuda.
 
2017-05-23  0:06:44 10284 [Note] InnoDB: Upgrading redo log: 2*16384 pages; LSN=3968922702569
 
2017-05-23  0:06:44 10284 [Note] InnoDB: Starting to delete and rewrite log files.
 
2017-05-23  0:06:44 10284 [Note] InnoDB: Setting log file G:\logs\ib_logfile101 size to 256 MB
 
2017-05-23  0:06:44 10284 [Note] InnoDB: Progress in MB:
 
 100 200
 
2017-05-23  0:07:03 10284 [Note] InnoDB: Setting log file G:\logs\ib_logfile1 size to 256 MB
 
2017-05-23  0:07:03 10284 [Note] InnoDB: Progress in MB:
 
 100 200
 
2017-05-23  0:07:25 10284 [Note] InnoDB: Renaming log file G:\logs\ib_logfile101 to G:\logs\ib_logfile0
 
2017-05-23  0:07:25 10284 [Note] InnoDB: New log files created, LSN=3968922702569
 
2017-05-23  0:07:27 10284 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:07:27 10284 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:07:29 10284 [Note] InnoDB: 128 out of 128 rollback segments are active.
 
2017-05-23  0:07:29 10284 [Note] InnoDB: Creating sys_virtual system tables.
 
2017-05-23  0:07:29 10284 [Note] InnoDB: Creating shared tablespace for temporary tables
 
2017-05-23  0:07:29 10284 [Note] InnoDB: Setting file 'G:\Database\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
 
2017-05-23  0:07:30 10284 [Note] InnoDB: File 'G:\Database\ibtmp1' size is now 12 MB.
 
2017-05-23  0:07:30 10284 [Note] InnoDB: 5.7.14 started; log sequence number 0
 
2017-05-23  0:07:30 13940 [Note] InnoDB: page_cleaner: 1000ms intended loop took 46816ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
 
2017-05-23  0:07:30 5280 [Note] InnoDB: Loading buffer pool(s) from G:\Database\ib_buffer_pool
 
2017-05-23  0:07:30 5280 [Note] InnoDB: Cannot open 'G:\Database\ib_buffer_pool' for reading: No such file or directory
 
2017-05-23  0:07:32 10284 [Note] Plugin 'FEEDBACK' is disabled.
 
2017-05-23  0:07:32 10284 [ERROR] C:\WebForce\MariaDB\bin\mysqld: unknown variable 'innodb_additional_mem_pool_size=8M'
 
2017-05-23  0:07:32 10284 [ERROR] Aborting

So I've removed innodb_additional_mem_pool_size from the ini file and started the service again.
For some reason the previously working table `test`.`googleplay_billing_log` became corrupted, so I tried to repair or at least drop it to restore from backup to no avail. The log mentioned SYS_TABLES, so I've decided to look into `information_schema`.`INNODB_SYS_TABLES` table.

2017-05-23  0:08:15 8288 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
 
2017-05-23  0:08:15 8288 [Warning] InnoDB: Using innodb_file_format_max is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
 
2017-05-23  0:08:15 8288 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-23  0:08:15 8288 [Note] InnoDB: Uses event mutexes
 
2017-05-23  0:08:15 8288 [Note] InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-23  0:08:15 8288 [Note] InnoDB: Number of pools: 1
 
2017-05-23  0:08:15 8288 [Note] InnoDB: Using generic crc32 instructions
 
2017-05-23  0:08:15 8288 [Note] InnoDB: Initializing buffer pool, total size = 20G, instances = 8, chunk size = 128M
 
2017-05-23  0:08:16 8288 [Note] InnoDB: Completed initialization of buffer pool
 
2017-05-23  0:08:16 8288 [Note] InnoDB: Highest supported file format is Barracuda.
 
*2017-05-23  0:08:18 8288 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:08:18 8288 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655*
 
2017-05-23  0:08:20 8288 [Note] InnoDB: 128 out of 128 rollback segments are active.
 
2017-05-23  0:08:20 8288 [Note] InnoDB: Creating shared tablespace for temporary tables
 
2017-05-23  0:08:20 8288 [Note] InnoDB: Setting file 'G:\Database\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
 
2017-05-23  0:08:21 8288 [Note] InnoDB: File 'G:\Database\ibtmp1' size is now 12 MB.
 
2017-05-23  0:08:21 8288 [Note] InnoDB: Waiting for purge to start
 
2017-05-23  0:08:21 8288 [Note] InnoDB: 5.7.14 started; log sequence number 3968922705248
 
2017-05-23  0:08:21 3444 [Note] InnoDB: page_cleaner: 1000ms intended loop took 5298ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
 
2017-05-23  0:08:21 9588 [Note] InnoDB: Loading buffer pool(s) from G:\Database\ib_buffer_pool
 
2017-05-23  0:08:22 9588 [Note] InnoDB: Buffer pool(s) load completed at 170523  0:08:22
 
2017-05-23  0:08:22 8288 [Note] Plugin 'FEEDBACK' is disabled.
 
2017-05-23  0:08:22 8288 [Note] Server socket created on IP: '::'.
 
2017-05-23  0:08:22 11188 [Note] Event Scheduler: scheduler thread started with id 6
 
2017-05-23  0:08:22 8288 [Note] C:\WebForce\MariaDB\bin\mysqld: ready for connections.
 
Version: '10.2.6-MariaDB-log'  socket: ''  port: 3306  mariadb.org binary distribution
 
2017-05-23  0:08:22 13296 [Note] Detected table cache mutex contention at instance 1: 44% waits. Additional table cache instance activated. Number of instances after activation: 2.
 
2017-05-23  0:11:08 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:11:08 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:11:08 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:11:08 12184 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:14:57 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:14:57 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:14:57 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:14:57 12184 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:14:59 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:14:59 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:14:59 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:14:59 12184 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:15:27 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:15:27 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:15:27 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:15:27 12184 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:17:03 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:17:03 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:17:03 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:17:03 12184 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:21:39 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:21:39 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:21:39 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:21:39 12184 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:32:00 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:32:00 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:32:00 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:32:00 12184 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:36:03 12184 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:36:03 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:36:03 12184 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:36:03 12184 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` does not exist in the InnoDB internal data dictionary though MariaDB is trying to drop it. Have you copied the .frm file of the table to the MariaDB database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:36:04 12184 [ERROR] InnoDB: Operating system error number 80 in a file operation.
 
2017-05-23  0:36:04 12184 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
 
2017-05-23  0:36:04 12184 [ERROR] InnoDB: Cannot create file '.\test\googleplay_billing_log.ibd'
 
2017-05-23  0:36:04 12184 [ERROR] InnoDB: The file '.\test\googleplay_billing_log.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\test\googleplay_billing_log.ibd' under the 'datadir' of MySQL.
 
2017-05-23  0:41:24 12612 [Note] C:\WebForce\MariaDB\bin\mysqld (unknown): Normal shutdown
 
 
 
2017-05-23  0:41:25 12612 [Note] Event Scheduler: Killing the scheduler thread, thread id 6
 
2017-05-23  0:41:25 12612 [Note] Event Scheduler: Waiting for the scheduler thread to reply
 
2017-05-23  0:41:25 12612 [Note] Event Scheduler: Stopped
 
2017-05-23  0:41:25 12612 [Note] Event Scheduler: Purging the queue. 1 events
 
2017-05-23  0:41:25 3692 [Note] InnoDB: FTS optimize thread exiting.
 
2017-05-23  0:41:25 12612 [Note] InnoDB: Starting shutdown...
 
2017-05-23  0:41:25 9588 [Note] InnoDB: Dumping buffer pool(s) to G:\Database\ib_buffer_pool
 
2017-05-23  0:41:25 9588 [Note] InnoDB: Buffer pool(s) dump completed at 170523  0:41:25
 
2017-05-23  0:41:27 12612 [Note] InnoDB: Shutdown completed; log sequence number 3968965866587
 
2017-05-23  0:41:27 12612 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
 
2017-05-23  0:41:27 12612 [Note] C:\WebForce\MariaDB\bin\mysqld: Shutdown complete
 
 
 
2017-05-23  0:41:27 8644 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-23  0:41:27 8644 [Note] InnoDB: Uses event mutexes
 
2017-05-23  0:41:27 8644 [Note] InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-23  0:41:27 8644 [Note] InnoDB: Number of pools: 1
 
2017-05-23  0:41:27 8644 [Note] InnoDB: Using generic crc32 instructions
 
2017-05-23  0:41:27 8644 [Note] InnoDB: Initializing buffer pool, total size = 20G, instances = 8, chunk size = 128M
 
2017-05-23  0:41:28 8644 [Note] InnoDB: Completed initialization of buffer pool
 
2017-05-23  0:41:28 8644 [Note] InnoDB: Highest supported file format is Barracuda.
 
2017-05-23  0:41:29 8644 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:41:29 8644 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:41:30 8644 [Note] InnoDB: 128 out of 128 rollback segments are active.
 
2017-05-23  0:41:30 8644 [Note] InnoDB: Creating shared tablespace for temporary tables
 
2017-05-23  0:41:30 8644 [Note] InnoDB: Setting file 'G:\Database\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
 
2017-05-23  0:41:30 8644 [Note] InnoDB: File 'G:\Database\ibtmp1' size is now 12 MB.
 
2017-05-23  0:41:30 8644 [Note] InnoDB: 5.7.14 started; log sequence number 3968965866587
 
2017-05-23  0:41:30 7884 [Note] InnoDB: Loading buffer pool(s) from G:\Database\ib_buffer_pool
 
2017-05-23  0:41:30 8644 [Note] Plugin 'FEEDBACK' is disabled.
 
2017-05-23  0:41:30 8644 [Note] Server socket created on IP: '::'.
 
2017-05-23  0:41:30 5148 [Note] Event Scheduler: scheduler thread started with id 6
 
2017-05-23  0:41:30 8644 [Note] C:\WebForce\MariaDB\bin\mysqld: ready for connections.
 
Version: '10.2.6-MariaDB-log'  socket: ''  port: 3306  mariadb.org binary distribution
 
2017-05-23  0:42:23 7884 [Note] InnoDB: Buffer pool(s) load completed at 170523  0:42:23
 
2017-05-23  0:42:50 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:42:50 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:42:50 9744 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:42:50 9744 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:43:02 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:43:02 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:43:02 9744 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:43:02 9744 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:43:03 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:43:03 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:43:03 9744 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:43:03 9744 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:43:58 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:43:58 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:43:58 9744 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:43:58 9744 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:44:13 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:44:13 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:44:13 9744 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:44:13 9744 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:44:17 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:44:17 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:44:17 9744 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:44:17 9744 [Warning] InnoDB: Cannot open table test/googleplay_billing_log from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:44:33 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:44:33 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
2017-05-23  0:44:33 9744 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-05-23  0:44:33 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` does not exist in the InnoDB internal data dictionary though MariaDB is trying to drop it. Have you copied the .frm file of the table to the MariaDB database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-05-23  0:44:34 9744 [ERROR] InnoDB: Operating system error number 80 in a file operation.
 
2017-05-23  0:44:34 9744 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
 
2017-05-23  0:44:34 9744 [ERROR] InnoDB: Cannot create file '.\test\googleplay_billing_log.ibd'
 
2017-05-23  0:44:34 9744 [ERROR] InnoDB: The file '.\test\googleplay_billing_log.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\test\googleplay_billing_log.ibd' under the 'datadir' of MySQL.
 
2017-05-23  0:44:48 9744 [ERROR] InnoDB: Operating system error number 80 in a file operation.
 
2017-05-23  0:44:48 9744 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
 
2017-05-23  0:44:48 9744 [ERROR] InnoDB: Cannot create file '.\test\googleplay_billing_log.ibd'
 
2017-05-23  0:44:48 9744 [ERROR] InnoDB: The file '.\test\googleplay_billing_log.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\test\googleplay_billing_log.ibd' under the 'datadir' of MySQL.
 
2017-05-23  0:45:05 9744 [ERROR] InnoDB: Operating system error number 80 in a file operation.
 
2017-05-23  0:45:05 9744 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
 
2017-05-23  0:45:05 9744 [ERROR] InnoDB: Cannot create file '.\test\googleplay_billing_log.ibd'
 
2017-05-23  0:45:05 9744 [ERROR] InnoDB: The file '.\test\googleplay_billing_log.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\test\googleplay_billing_log.ibd' under the 'datadir' of MySQL.
 
2017-05-23  0:46:35 9744 [ERROR] InnoDB: Operating system error number 80 in a file operation.
 
2017-05-23  0:46:35 9744 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
 
2017-05-23  0:46:35 9744 [ERROR] InnoDB: Cannot create file '.\test\googleplay_billing_log.ibd'
 
2017-05-23  0:46:35 9744 [ERROR] InnoDB: The file '.\test\googleplay_billing_log.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\test\googleplay_billing_log.ibd' under the 'datadir' of MySQL.
 
2017-05-23  0:47:26 9744 [ERROR] InnoDB: Operating system error number 80 in a file operation.
 
2017-05-23  0:47:26 9744 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
 
2017-05-23  0:47:26 9744 [ERROR] InnoDB: Cannot create file '.\test\googleplay_billing_log.ibd'
 
2017-05-23  0:47:26 9744 [ERROR] InnoDB: The file '.\test\googleplay_billing_log.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '.\test\googleplay_billing_log.ibd' under the 'datadir' of MySQL.
 
2017-05-23  0:50:06 9744 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-05-23  0:50:06 9744 [ERROR] InnoDB: Table `test`.`googleplay_billing_log` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483655
 
*170523  0:50:06 [ERROR] mysqld got exception 0xc0000005 ;*
 
...

Here's .sql file from this table's backup:

-- MySQL dump 10.16  Distrib 10.1.22-MariaDB, for Win64 (AMD64)
 
--
 
-- Host: 127.0.0.1    Database: test
 
-- ------------------------------------------------------
 
-- Server version	10.1.22-MariaDB
 
 
 
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
 
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
 
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
 
/*!40101 SET NAMES cp1251 */;
 
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
 
/*!40103 SET TIME_ZONE='+00:00' */;
 
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='' */;
 
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
 
 
 
--
 
-- Table structure for table `googleplay_billing_log`
 
--
 
 
 
DROP TABLE IF EXISTS `googleplay_billing_log`;
 
/*!40101 SET @saved_cs_client     = @@character_set_client */;
 
/*!40101 SET character_set_client = utf8 */;
 
CREATE TABLE `googleplay_billing_log` (
 
  `id` int(10) NOT NULL AUTO_INCREMENT,
 
  `post_dump` text,
 
  `type` varchar(10) DEFAULT '',
 
  `script_result` varchar(255) DEFAULT '',
 
  `user_login` varchar(25) DEFAULT '',
 
  `order_number` varchar(255) DEFAULT '',
 
  `timestamp` timestamp NULL DEFAULT CURRENT_TIMESTAMP,
 
  PRIMARY KEY (`id`),
 
  KEY `user_login` (`user_login`),
 
  KEY `order_number` (`order_number`)
 
) ENGINE=InnoDB AUTO_INCREMENT=941 DEFAULT CHARSET=cp1251 ROW_FORMAT=DYNAMIC COMMENT='Лог постбэков Google Play' `page_compressed`=1;
 
/*!40101 SET character_set_client = @saved_cs_client */;
 
 
 
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;
 
 
 
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
 
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
 
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
 
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
 
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
 
 
 
-- Dump completed on 2017-05-21 20:30:29

Comment by Elena Stepanova [ 2017-06-01 ]

Thanks for the report, reproducible as described.

On 10.1 server (clean, with all defaults)

 
SET GLOBAL innodb_file_format=Barracuda;
 
 
 
CREATE TABLE `t1` (
 
  `id` int(10) NOT NULL AUTO_INCREMENT,
 
  PRIMARY KEY (`id`)
 
) ENGINE=InnoDB ROW_FORMAT=DYNAMIC PAGE_COMPRESSED=1;
 
 
 
shutdown; # Let it shutdown normally

Start 10.2 on the same datadir, all defaults.

Server log after 10.2 startup

 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Uses event mutexes
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Compressed tables use zlib 1.2.8
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Using Linux native AIO
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Number of pools: 1
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Using SSE2 crc32 instructions
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Completed initialization of buffer pool
 
2017-06-01 20:03:02 139730597005056 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Highest supported file format is Barracuda.
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Upgrading redo log: 2*3072 pages; LSN=1620598
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Starting to delete and rewrite log files.
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
 
2017-06-01 20:03:02 139731349037120 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: New log files created, LSN=1620598
 
2017-06-01 20:03:03 139731349037120 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-06-01 20:03:03 139731349037120 [ERROR] InnoDB: Table `test`.`t1` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483649
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: 128 out of 128 rollback segments are active.
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: Creating sys_virtual system tables.
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: Creating shared tablespace for temporary tables
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: Waiting for purge to start
 
2017-06-01 20:03:03 139731349037120 [Note] InnoDB: 5.7.18 started; log sequence number 0
 
2017-06-01 20:03:03 139730377238272 [Note] InnoDB: Loading buffer pool(s) from /data/bld/10.1/data/ib_buffer_pool
 
2017-06-01 20:03:03 139730377238272 [Note] InnoDB: Cannot open '/data/bld/10.1/data/ib_buffer_pool' for reading: No such file or directory
 
2017-06-01 20:03:03 139731349037120 [Note] Plugin 'FEEDBACK' is disabled.
 
2017-06-01 20:03:03 139731349037120 [Note] Server socket created on IP: '::'.
 
2017-06-01 20:03:03 139731349037120 [Note] Reading of all Master_info entries succeded
 
2017-06-01 20:03:03 139731349037120 [Note] Added new Master_info '' to hash table
 
2017-06-01 20:03:03 139731349037120 [Note] /data/bld/10.2/bin/mysqld: ready for connections.
 
Version: '10.2.7-MariaDB-debug'  socket: '/data/bld/10.1/data/tmp/mysql.sock'  port: 3306  Source distribution
 
2017-06-01 20:03:05 139731322357504 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-06-01 20:03:05 139731322357504 [ERROR] InnoDB: Table `test`.`t1` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483649
 
2017-06-01 20:03:05 139731322357504 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-06-01 20:03:05 139731322357504 [Warning] InnoDB: Cannot open table test/t1 from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.

On 10.2

 
MariaDB [test]> show create table t1;
 
ERROR 1932 (42S02): Table 'test.t1' doesn't exist in engine
 
MariaDB [test]> select * from information_schema.innodb_sys_tables;
 
ERROR 2013 (HY000): Lost connection to MySQL server during query

10.2 aad8cefd2d0e49acb9f8ae3ebaa0e3b90f27b89c

 
2017-06-01 20:04:30 139731322357504 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-06-01 20:04:30 139731322357504 [ERROR] InnoDB: Table `test`.`t1` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483649
 
2017-06-01 20:04:30 139731322357504 [ERROR] InnoDB: incorrect flags in SYS_TABLES
 
2017-06-01 20:04:30 139731322357504 [Warning] InnoDB: Cannot open table test/t1 from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/
 
doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
 
2017-06-01 20:04:41 139731322357504 [ERROR] InnoDB: SYS_TABLES::TYPE=1697 page_compression:0 page_compression_level:3 atomic_blobs:1
 
2017-06-01 20:04:41 139731322357504 [ERROR] InnoDB: Table `test`.`t1` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=1697 SYS_TABLES.N_COLS=2147483649
 
mysqld: /data/src/10.2/storage/innobase/dict/dict0mem.cc:176: void dict_mem_table_free(dict_table_t*): Assertion `table->magic_n == 76333786' failed.
 
170601 20:04:41 [ERROR] mysqld got signal 6 ;
 
 
 
#7  0x00007f15b9b67ee2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 
#8  0x00007f15bccef4a5 in dict_mem_table_free (table=0x7f1548021fe8) at /data/src/10.2/storage/innobase/dict/dict0mem.cc:176
 
#9  0x00007f15bca625b8 in i_s_sys_tables_fill_table (thd=0x7f1548000b00, tables=0x7f15480110f0) at /data/src/10.2/storage/innobase/handler/i_s.cc:6158
 
#10 0x00007f15bc53bc32 in get_schema_tables_result (join=0x7f1548012298, executed_place=PROCESSED_BY_JOIN_EXEC) at /data/src/10.2/sql/sql_show.cc:8263
 
#11 0x00007f15bc4d9df9 in JOIN::exec_inner (this=0x7f1548012298) at /data/src/10.2/sql/sql_select.cc:3437
 
#12 0x00007f15bc4d94d4 in JOIN::exec (this=0x7f1548012298) at /data/src/10.2/sql/sql_select.cc:3274
 
#13 0x00007f15bc4da67d in mysql_select (thd=0x7f1548000b00, tables=0x7f15480110f0, wild_num=1, fields=..., conds=0x0, og_num=0, order=0x0, group=0x0, having=0x0, proc_param=0x0, select_options=2684619520, result=0x7f1548012278, unit=0x7f15480045e0, select_lex=0x7f1548004d18) at /data/src/10.2/sql/sql_select.cc:3668
 
#14 0x00007f15bc4ceff2 in handle_select (thd=0x7f1548000b00, lex=0x7f1548004518, result=0x7f1548012278, setup_tables_done_option=0) at /data/src/10.2/sql/sql_select.cc:373
 
#15 0x00007f15bc49b2f9 in execute_sqlcom_select (thd=0x7f1548000b00, all_tables=0x7f15480110f0) at /data/src/10.2/sql/sql_parse.cc:6433
 
#16 0x00007f15bc491338 in mysql_execute_command (thd=0x7f1548000b00) at /data/src/10.2/sql/sql_parse.cc:3448
 
#17 0x00007f15bc49eccc in mysql_parse (thd=0x7f1548000b00, rawbuf=0x7f1548010e98 "select * from information_schema.innodb_sys_tables", length=50, parser_state=0x7f15bbd53250, is_com_multi=false, is_next_command=false) at /data/src/10.2/sql/sql_parse.cc:7870
 
#18 0x00007f15bc48cda4 in dispatch_command (command=COM_QUERY, thd=0x7f1548000b00, packet=0x7f1548017fc1 "select * from information_schema.innodb_sys_tables", packet_length=50, is_com_multi=false, is_next_command=false) at /data/src/10.2/sql/sql_parse.cc:1812
 
#19 0x00007f15bc48b714 in do_command (thd=0x7f1548000b00) at /data/src/10.2/sql/sql_parse.cc:1362
 
#20 0x00007f15bc5d6569 in do_handle_one_connection (connect=0x7f15c03196a0) at /data/src/10.2/sql/sql_connect.cc:1354
 
#21 0x00007f15bc5d62f6 in handle_one_connection (arg=0x7f15c03196a0) at /data/src/10.2/sql/sql_connect.cc:1260
 
#22 0x00007f15bbaac494 in start_thread (arg=0x7f15bbd54700) at pthread_create.c:333
 
#23 0x00007f15b9c2493f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Whether mysql_upgrade is run or not is irrelevant here, because the table isn't loaded anyway.

Comment by Marko Mäkelä [ 2017-06-12 ]

As noted in MDEV-13015, this compatibility problem was introduced in MariaDB 10.2.2 when the unused table flag SHARED_SPACE was added to MariaDB and the PAGE_COMPRESSION, PAGE_COMPRESSION_LEVEL and ATOMIC_WRITES flags were shifted by 1 position.

Comment by Marko Mäkelä [ 2017-06-13 ]

This bug affects the creation and opening of tables that have the following attributes:
ATOMIC_WRITES
PAGE_COMPRESSION
PAGE_COMPRESSION_LEVEL

The ATOMIC_WRITES attribute was removed from MariaDB 10.2.4. It also removed some compatibility tests from dict_tf_is_valid() and dict_sys_tables_type_validate() which would have been useful for MDEV-13015.

If the ATOMIC_WRITES attribute was set to ON or OFF in MariaDB 10.1, then versions 10.2.2 and 10.2.3 could refuse to load such tables. From version 10.2.4 on, MariaDB would ignore this attribute.

If the PAGE_COMPRESSION or PAGE_COMPRESSION_LEVEL is used in MariaDB 10.1, then versions 10.2.2 through 10.2.6 may misinterpret the attribute, and in some cases refuse to open the table. In other cases, the data could be misinterpreted due to the incompatible interpretation of the metadata.

I intend to fix this compatibility bug by restoring the old 10.1 format of the SYS_TABLES.TYPE, without implementing any sort of corrective action (like in MDEV-11623).

This means that if any of the attributes ATOMIC_WRITES, PAGE_COMPRESSION or PAGE_COMPRESSION_LEVEL were used in CREATE TABLE or ALTER TABLE on MariaDB 10.2.2, 10.2.3, 10.2.4, 10.2.5, 10.2.6 or 10.3.0, then the tables would be inaccessible in other versions of MariaDB. You could export, drop and import the affected tables when upgrading from the affected versions to 10.2.7 or 10.3.1 or later.

My intended fix also means that MDEV-12309 has to be revisited, because there would no longer be a SHARED_SPACE field in 10.2.

Comment by Marko Mäkelä [ 2017-06-13 ]

MariaDB 10.0 is properly rejecting to open tables with invalid SYS_TABLES.TYPE, as validated by the test that I added: innodb.table_flags.
MariaDB 10.1 was hitting an assertion failure if the ATOMIC_WRITES field contained the value 3. I fixed that.

For MariaDB 10.2, extra care is needed to ensure reasonable compatibility with MariaDB 10.2.6 (the first GA release with this incompatibility bug present) and MySQL 5.7 (CREATE TABLE…TABLESPACE could be interpreted like CREATE TABLE…PAGE_COMPRESSED in the MariaDB 10.1 format of SYS_TABLES.TYPE).

Comment by Marko Mäkelä [ 2017-06-14 ]

I have a solution with one drawback: Tables created with PAGE_COMPRESSED=YES in MariaDB 10.2.2‥10.2.6 or 10.3.0 would not be loadable in 10.2.7, 10.3.1 or later. Tables created in 10.2.0, 10.2.1 or 10.1.x should be just fine.
The highlight of the drawback is that 10.2.6 is the first (and so far the only) GA release in the 10.2.6, and we would be breaking data dictionary compatibility with 10.2.6.
Here is what I tested:

LATEST=/mariadb/10.2/build
 
GA=/mariadb/10.2.6
 
cd $GA
 
cat > mysql-test/suite/innodb/t/upgrade.test << EOF
 
--source include/have_innodb.inc
 
create table tp1 (a serial)engine=innodb page_compressed=yes page_compression_level=1;
 
create table tp2 (a serial)engine=innodb page_compressed=yes page_compression_level=2;
 
create table tp4 (a serial)engine=innodb page_compressed=yes page_compression_level=4;
 
create table tp8 (a serial)engine=innodb page_compressed=yes page_compression_level=8;
 
create table tp9 (a serial)engine=innodb page_compressed=yes page_compression_level=9;
 
create table tp0 (a serial)engine=innodb page_compressed=yes page_compression_level=0;
 
EOF
 
cd build/mysql-test
 
./mysql-test-run innodb.upgrade
 
gdb --args $LATEST/sql/mysqld --defaults-group-suffix=.1 --defaults-file=$LATEST/mysql-test/var/my.cnf --innodb --datadir $GA/build/mysql-test/var/log/innodb.upgrade-innodb/mysqld.1/data
 
run

The above would create a bunch of tables in 10.2.6 and then start up a 10.2 server with my fix (with the removal of SHARED_SPACE flag, moving the PAGE_COMPRESSED and PAGE_COMPRESSION_LEVEL flags back to the original 10.1 position).
To access the tables, we have to fire up a client:

LATEST=/mariadb/10.2/build
 
mysql --defaults-file=$LATEST/mysql-test/var/my.cnf -uroot test << EOF
 
show create table tp1;
 
show create table tp2;
 
show create table tp4;
 
show create table tp8;
 
show create table tp9;
 
EOF

Each of these tables will be refused access, with the following type of error message:

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

The reason for this rejection is that the affected MariaDB server versions (10.2.2‥10.2.6) would appear to leave the PAGE_COMPRESSED flag clear while writing a nonzero value to the 4-bit field PAGE_COMPRESSION_LEVEL.
Let us call the misplaced bitfields PAGE_COMPRESSED_10_2_2 and PAGE_COMPRESSION_LEVEL_10_2_2. The correct PAGE_COMPRESSED flag would remain clear, because 10.2.2 allocated the SHARED_SPACE flag in its place, and it would never set that flag. On the other hand, PAGE_COMPRESSED_10_2_2 would reside in the high-order bit of PAGE_COMPRESSION_LEVEL. So, with my proposed fix, MariaDB would interpret the table as having PAGE_COMPRESSION_LEVEL>=8 but PAGE_COMPRESSED=NO, which is an invalid combination.

Also the field ATOMIC_WRITES is affected. But it would only be written as nonzero by 10.2.2 and 10.2.3; the field was removed in 10.2.4.

Similar messages be output when trying to open a table that was created in MySQL 5.7 with the TABLESPACE attribute (MDEV-12309). In that case, after this fix, it would be interpreted as PAGE_COMPRESSED=YES but with PAGE_COMPRESSION_LEVEL=0, which is an invalid combination.

Last but not least, what about downgrade to 10.2.6? If any table was created with the attribute PAGE_COMPRESSED=YES, 10.2.6 should refuse to load it, interpreting that it was created with the unsupported TABLESPACE attribute of MySQL 5.7. (The case of PAGE_COMPRESSION_LEVEL>0 but PAGE_COMPRESSED=NO is not allowed, so we do not need to care about PAGE_COMPRESSED=NO PAGE_COMPRESSION_LEVEL=9 being interpreted by 10.2.6 as PAGE_COMPRESSED=YES PAGE_COMPRESSION_LEVEL=2.)

Comment by Marko Mäkelä [ 2017-06-14 ]

I implemented a solution and merged a test that interprets the incompatible SYS_TABLES.TYPE of tables created with PAGE_COMPRESSED=YES on MariaDB 10.2.2…10.2.6. It passed my manual test outlined above. Once elenst confirms that it works with upgrades from MySQL 5.7, MariaDB 10.1 and MariaDB 10.2.6, I will push it to 10.2.

Generated at Thu Feb 08 08:01:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.