[MDEV-21572] buf_page_get_gen() should apply buffered page initialized redo log during recovery - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.1, 10.2, 10.3, 10.4, 10.5
Fix Version/s: 10.2.32, 10.3.23, 10.4.13, 10.5.3
Component/s: Storage Engine - InnoDB, Tests
Labels:
- recovery

Description

Unfortunately, logs are no longer available. So, it's just for a record, until it fails again.

10.3 4923604ee2fba372f28c856a3f41274f winx64-debug
innodb.leaf_page_corrupted_during_recovery 'innodb' w4 [ fail ]
Test ended at 2019-12-29 15:11:24

CURRENT_TEST: innodb.leaf_page_corrupted_during_recovery
mysqltest: At line 51: query 'SELECT * FROM t1 WHERE PK = 1' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:
CREATE TABLE t1 (pk INT PRIMARY KEY, c CHAR(255))ENGINE=InnoDB STATS_PERSISTENT=0;
SET GLOBAL INNODB_LIMIT_OPTIMISTIC_INSERT_DEBUG = 2;
INSERT INTO t1 VALUES(1, 'sql'), (2, 'server'), (3, 'mariadb'),
(4, 'mariadb'), (5, 'test1'), (6, 'test2'), (7, 'test3'),
(8, 'test4'), (9, 'test5'), (10, 'test6'), (11, 'test7'),
(12, 'test8');
SELECT COUNT(*) FROM t1;
COUNT(*)
12
UPDATE t1 SET c='best8' WHERE pk=12;
# Kill the server
# Corrupt the pages
SELECT * FROM t1 WHERE PK = 1;
ERROR 42000: Unknown storage engine 'InnoDB'
SELECT * FROM t1 WHERE PK = 1;


Server [mysqld.1 - pid: 7164, winpid: 7164, exit: 768] failed during test run
Server log from this test:
----------SERVER LOG START-----------
2019-12-29 15:11:11 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe (mysqld 10.3.22-MariaDB-debug-log) starting as process 7436 ...
2019-12-29 15:11:11 0 [Note] Plugin 'SEQUENCE' is disabled.
2019-12-29 15:11:11 0 [Note] Plugin 'partition' is disabled.
2019-12-29 15:11:11 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2019-12-29 15:11:11 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-12-29 15:11:11 0 [Note] InnoDB: Uses event mutexes
2019-12-29 15:11:11 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-29 15:11:11 0 [Note] InnoDB: Number of pools: 1
2019-12-29 15:11:11 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-12-29 15:11:11 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2019-12-29 15:11:11 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-29 15:11:12 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-12-29 15:11:12 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-12-29 15:11:12 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-12-29 15:11:12 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2019-12-29 15:11:12 0 [Note] InnoDB: Waiting for purge to start
2019-12-29 15:11:12 0 [Note] InnoDB: 10.3.22 started; log sequence number 1636581; transaction id 34
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_MUTEXES' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_CMP' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'user_variables' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
2019-12-29 15:11:12 0 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
2019-12-29 15:11:12 0 [Warning] D:/winx64-debug/build/sql//Debug/mysqld.exe: unknown option '--loose-pam-debug'
2019-12-29 15:11:12 0 [Note] Server socket created on IP: '::'.
2019-12-29 15:11:12 0 [Note] Reading of all Master_info entries succeeded
2019-12-29 15:11:12 0 [Note] Added new Master_info '' to hash table
2019-12-29 15:11:12 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe: ready for connections.
Version: '10.3.22-MariaDB-debug-log' socket: '' port: 16060 Source distribution
2019-12-29 15:11:12 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe (initiated by: root[root] @ localhost [::1]): Normal shutdown
2019-12-29 15:11:12 0 [Note] Event Scheduler: Purging the queue. 0 events
2019-12-29 15:11:12 0 [Note] InnoDB: FTS optimize thread exiting.
2019-12-29 15:11:12 0 [Note] InnoDB: Starting shutdown...
2019-12-29 15:11:12 0 [Note] InnoDB: Dumping buffer pool(s) to D:\winx64-debug\build\mysql-test\var\4\mysqld.1\data\ib_buffer_pool
2019-12-29 15:11:12 0 [Note] InnoDB: Instance 0, restricted to 128 pages due to innodb_buf_pool_dump_pct=25
2019-12-29 15:11:12 0 [Note] InnoDB: Buffer pool(s) dump completed at 191229 15:11:12
2019-12-29 15:11:13 0 [Note] InnoDB: Shutdown completed; log sequence number 1646317; transaction id 38
2019-12-29 15:11:13 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-12-29 15:11:13 0 [Note] Debug sync points hit: 1514
2019-12-29 15:11:13 0 [Note] Debug sync points executed: 0
2019-12-29 15:11:13 0 [Note] Debug sync points max active per thread: 0
2019-12-29 15:11:13 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe: Shutdown complete

2019-12-29 15:11:15 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe (mysqld 10.3.22-MariaDB-debug-log) starting as process 9788 ...
2019-12-29 15:11:15 0 [Note] Plugin 'SEQUENCE' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'partition' is disabled.
2019-12-29 15:11:15 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2019-12-29 15:11:15 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-12-29 15:11:15 0 [Note] InnoDB: Uses event mutexes
2019-12-29 15:11:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-29 15:11:15 0 [Note] InnoDB: Number of pools: 1
2019-12-29 15:11:15 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-12-29 15:11:15 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2019-12-29 15:11:15 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-29 15:11:15 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-12-29 15:11:15 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-12-29 15:11:15 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-12-29 15:11:15 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2019-12-29 15:11:15 0 [Note] InnoDB: Waiting for purge to start
2019-12-29 15:11:15 0 [Note] InnoDB: 10.3.22 started; log sequence number 1646317; transaction id 40
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_MUTEXES' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_CMP' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'user_variables' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
2019-12-29 15:11:15 0 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
2019-12-29 15:11:15 0 [Warning] D:/winx64-debug/build/sql//Debug/mysqld.exe: unknown option '--loose-pam-debug'
2019-12-29 15:11:15 0 [Note] Server socket created on IP: '::'.
2019-12-29 15:11:15 0 [Note] Reading of all Master_info entries succeeded
2019-12-29 15:11:15 0 [Note] Added new Master_info '' to hash table
2019-12-29 15:11:15 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe: ready for connections.
Version: '10.3.22-MariaDB-debug-log' socket: '' port: 16060 Source distribution
2019-12-29 15:11:16 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe (mysqld 10.3.22-MariaDB-debug-log) starting as process 9876 ...
2019-12-29 15:11:16 0 [Note] Plugin 'SEQUENCE' is disabled.
2019-12-29 15:11:16 0 [Note] Plugin 'partition' is disabled.
2019-12-29 15:11:16 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2019-12-29 15:11:16 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-12-29 15:11:16 0 [Note] InnoDB: Uses event mutexes
2019-12-29 15:11:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-29 15:11:16 0 [Note] InnoDB: Number of pools: 1
2019-12-29 15:11:16 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-12-29 15:11:16 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2019-12-29 15:11:16 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-29 15:11:17 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1646317
2019-12-29 15:11:17 0 [Note] InnoDB: Starting final batch to recover 1 pages from redo log.
2019-12-29 15:11:17 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:17 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:17 0 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:17 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:17 0 [ERROR] InnoDB: Failed to read file '.\test\t1.ibd' at offset 19: Page read from tablespace is corrupted.
2019-12-29 15:11:17 0 [Note] InnoDB: Set innodb_force_recovery=1 to ignore corrupted pages.
2019-12-29 15:11:17 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[2009] with error Data structure corruption
2019-12-29 15:11:18 0 [Note] InnoDB: Starting shutdown...
2019-12-29 15:11:18 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-12-29 15:11:18 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_MUTEXES' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_CMP' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'user_variables' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
2019-12-29 15:11:18 0 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
2019-12-29 15:11:18 0 [Warning] D:/winx64-debug/build/sql//Debug/mysqld.exe: unknown option '--loose-pam-debug'
2019-12-29 15:11:18 0 [Note] Server socket created on IP: '::'.
2019-12-29 15:11:18 0 [Note] Reading of all Master_info entries succeeded
2019-12-29 15:11:18 0 [Note] Added new Master_info '' to hash table
2019-12-29 15:11:18 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe: ready for connections.
Version: '10.3.22-MariaDB-debug-log' socket: '' port: 16060 Source distribution
2019-12-29 15:11:18 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe (initiated by: root[root] @ localhost [127.0.0.1]): Normal shutdown
2019-12-29 15:11:18 0 [Note] Event Scheduler: Purging the queue. 0 events
2019-12-29 15:11:18 0 [Note] Debug sync points hit: 238
2019-12-29 15:11:18 0 [Note] Debug sync points executed: 0
2019-12-29 15:11:18 0 [Note] Debug sync points max active per thread: 0
2019-12-29 15:11:18 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe: Shutdown complete

2019-12-29 15:11:20 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe (mysqld 10.3.22-MariaDB-debug-log) starting as process 8500 ...
2019-12-29 15:11:20 0 [Note] Plugin 'SEQUENCE' is disabled.
2019-12-29 15:11:20 0 [Note] Plugin 'partition' is disabled.
2019-12-29 15:11:20 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2019-12-29 15:11:20 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-12-29 15:11:20 0 [Note] InnoDB: Uses event mutexes
2019-12-29 15:11:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-29 15:11:20 0 [Note] InnoDB: Number of pools: 1
2019-12-29 15:11:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-12-29 15:11:20 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2019-12-29 15:11:20 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-29 15:11:20 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1646317
2019-12-29 15:11:20 0 [Note] InnoDB: Starting final batch to recover 1 pages from redo log.
2019-12-29 15:11:20 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:20 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:20 0 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:20 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:20 0 [ERROR] InnoDB: Failed to read file '.\test\t1.ibd' at offset 19: Page read from tablespace is corrupted.
2019-12-29 15:11:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-12-29 15:11:21 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-12-29 15:11:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-12-29 15:11:21 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-12-29 15:11:21 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2019-12-29 15:11:21 0 [Note] InnoDB: Waiting for purge to start
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 4 [Warning] InnoDB: Error code: 107 btr_pcur_open_low level: 0 called from file: D:\winx64-debug\build\src\storage\innobase\row\row0row.cc line: 1052 table: `test`.`t1` index: `PRIMARY`
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 0 [Note] InnoDB: 10.3.22 started; log sequence number 1647063; transaction id 44
2019-12-29 15:11:21 0 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_MUTEXES' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_CMP' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 0 [Note] Plugin 'user_variables' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 0 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 0 [Warning] D:/winx64-debug/build/sql//Debug/mysqld.exe: unknown option '--loose-pam-debug'
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 0 [Note] Server socket created on IP: '::'.
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 0 [Note] Reading of all Master_info entries succeeded
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 0 [Note] Added new Master_info '' to hash table
2019-12-29 15:11:21 0 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe: ready for connections.
Version: '10.3.22-MariaDB-debug-log' socket: '' port: 16060 Source distribution
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2019-12-29 15:11:21 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=5, page number=19]. You may have to recover from a backup.
2019-12-29 15:11:21 1 [Note] InnoDB: Uncompressed page, stored checksum in field1 1786080875, calculated checksums for field1: crc32 1044816981, innodb 593965754, page type 17855 == INDEX.none 3735928559, stored checksum in field2 1044816981, calculated checksums for field2: crc32 1044816981, innodb 834101323, none 3735928559, page LSN 0 1646109, low 4 bytes of LSN at page end 1646109, page number (if stored to page already) 19, space id (if created with >= MySQL-4.1.1 and stored already) 5
2019-12-29 15:11:21 1 [Note] InnoDB: Page may be an index page where index id is 25
2019-12-29 15:11:21 1 [Note] InnoDB: Index 25 is `PRIMARY` in table `test`.`t1`
2019-12-29 15:11:21 1 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library

Attachments

Issue Links

causes

MDEV-22369 Assertion `err == DB_SUCCESS' failed. in btr_block_get_func during crash recovery

Closed

MDEV-23380 InnoDB reads a page from disk despite parsing MLOG_INIT_FILE_PAGE2 record

Closed

MDEV-32042 Special handling of crash recovery in buf_page_get_gen() may cause overhead

Closed

relates to

MDEV-20755 InnoDB: Database page corruption on disk or a failed file read of tablespace upon prepare of mariabackup incremental backup

Closed

MDEV-23380 InnoDB reads a page from disk despite parsing MLOG_INIT_FILE_PAGE2 record

Closed

MDEV-24913 Assertion !recv_no_log_write in log_write_up_to()

Closed

MDEV-12699 Improve crash recovery of corrupted data pages

Closed

MDEV-20688 Recovery crashes after unnecessarily reading a corrupted page

Closed

(3 relates to)

Activity

People

Assignee:: Thirunarayanan Balathandayuthapani

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2020-01-26 17:35

Updated:: 2023-08-30 12:34

Resolved:: 2020-03-23 11:16

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.