解决数据库Operation not allowed when innodb_forced_recovery > 0

332次阅读

没有评论

共计 10030 个字符，预计需要花费 26 分钟才能阅读完成。

解决数据库 Operation not allowed when innodb_forced_recovery > 0

请修改 my.cnf

innodb_force_recovery = 1

修改为

innodb_force_recovery = 0

在关闭时，参数 innodb_fast_shutdown 影响着表的存储引擎为 InnoDB 的行为。

该参数取值为 0、1、2

0 代表党 MySql 关闭时，InnoDB 需要完成所有的 full purge 和 merge insert buffer 操作，这会需要一些时间。1 代表不需要完成上述的 full purge ,merge insert buffer 操作，但是在缓冲池的一些数据脏页还是会刷新到磁盘。2 代表不完成 full purge ,merge insert buffer 操作，也不将缓冲池中的数据脏页写回磁盘，而是将日志都写入日志文件。这样不会有任何事物会丢失，但是 Mysql 数据库下次启动时，会执行 recovery
参数 Innodb_force_recovery 影响了整个 InnoDB 存储引擎的恢复状况。默认 0

测试：

环境：innodb_fast_shutdown = 2

innodb_flush_log_at_trx_commit = 2

sync_binlog = 0

innodb_force_recovery 影响整个 InnoDB 存储引擎的恢复状况。默认为 0，表示当需要恢复时执行所有的

恢复操作。当不能进行有效的恢复操作时，mysql 有可能无法启动，并记录下错误日志。
innodb_force_recovery 可以设置为 1 -6, 大的数字包含前面所有数字的影响。
当设置参数值大于 0 后，可以对表进行 select,create,drop 操作, 但 insert,update 或者 delete 这类操作

是不允许的。
1(SRV_FORCE_IGNORE_CORRUPT): 忽略检查到的 corrupt 页。
2(SRV_FORCE_NO_BACKGROUND): 阻止主线程的运行，如主线程需要执行 full purge 操作，会导致 crash。
3(SRV_FORCE_NO_TRX_UNDO): 不执行事务回滚操作。
4(SRV_FORCE_NO_IBUF_MERGE): 不执行插入缓冲的合并操作。
5(SRV_FORCE_NO_UNDO_LOG_SCAN): 不查看重做日志，InnoDB 存储引擎会将未提交的事务视为已提交。
6(SRV_FORCE_NO_LOG_REDO): 不执行前滚的操作。

测试一
破坏 xbb5.ibd 表
删除了数据页
innodb_force_recovery = 1-3 表不可用
报 ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/tmp/mysqld.sock’ 错误
innodb_force_recovery = 4-6 select * 可用，select count(*）不准缺
报 ERROR 2013 (HY000): Lost connection to MySQL server during query 错误

测试二
创建事务，不提交
root@test 04:32:32>begin;
Query OK, 0 rows affected (0.01 sec)

root@test 04:33:14>update test set b = b+100;
Query OK, 9999 rows affected (0.18 sec)
Rows matched: 9999 Changed: 9999 Warnings: 0

innodb_force_recovery =0 要检查回滚操作
130626 16:32:20 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 9999 row operations to undo
InnoDB: Trx id counter is 0 12544
InnoDB: Last MySQL binlog file position 0 920753, file name /vobiledata/mysqllog/mysql-bin.000245
InnoDB: Starting in background the rollback of uncommitted transactions
130626 16:32:21 InnoDB: Rolling back trx with id 0 12032, 9999 rows to undo

InnoDB: Progress in percents: 1130626 16:32:21 InnoDB: Started; log sequence number 0 4330016
130626 16:32:21 [Note] Recovering after a crash using /vobiledata/mysqllog/mysql-bin
130626 16:32:21 [Note] Starting crash recovery…
130626 16:32:21 [Note] Crash recovery finished.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97130626 16:32:21 [Note] Event Scheduler: Loaded 0 events
130626 16:32:21 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.1.57-log’ socket: ‘/tmp/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
98 99 100
InnoDB: Rolling back of trx id 0 12032 completed
130626 16:32:21 InnoDB: Rollback of non-prepared transactions completed

如果回滚数据多，恢复就相对的慢
innodb_force_recovery =2 阻止主线程的运行，如主线程需要执行 full purge 操作，会导致 crash。
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 9999 row operations to undo
InnoDB: Trx id counter is 0 15616
InnoDB: Last MySQL binlog file position 0 920753, file name /vobiledata/mysqllog/mysql-bin.000245
InnoDB: Starting in background the rollback of uncommitted transactions
130626 17:05:53 InnoDB: Rolling back trx with id 0 15104, 9999 rows to undo

InnoDB: Progress in percents: 1130626 17:05:53 InnoDB: Started; log sequence number 0 13016158
InnoDB: !!! innodb_force_recovery is set to 2 !!!
130626 17:05:53 [Note] Recovering after a crash using /vobiledata/mysqllog/mysql-bin
130626 17:05:53 [Note] Starting crash recovery…
130626 17:05:53 [Note] Crash recovery finished.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85130626 17:05:53 [Note] Event Scheduler: Loaded 0 events
130626 17:05:53 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.1.57-log’ socket: ‘/tmp/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 0 15104 completed
130626 17:05:53 InnoDB: Rollback of non-prepared transactions completed

innodb_force_recovery =3 不执行回滚操作

130626 16:33:53 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 9999 row operations to undo
InnoDB: Trx id counter is 0 13056
InnoDB: Last MySQL binlog file position 0 920753, file name /vobiledata/mysqllog/mysql-bin.000245
130626 16:33:53 InnoDB: Started; log sequence number 0 6497918
InnoDB: !!! innodb_force_recovery is set to 3 !!!
130626 16:33:53 [Note] Recovering after a crash using /vobiledata/mysqllog/mysql-bin
130626 16:33:53 [Note] Starting crash recovery…
130626 16:33:53 [Note] Crash recovery finished.
130626 16:33:53 [Note] Event Scheduler: Loaded 0 events
130626 16:33:53 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.1.57-log’ socket: ‘/tmp/mysqld.sock’ port: 3306 MySQL Community Server (GPL)

innodb_force_recovery =5 不查看重做日志，innodb 存储引擎会将未提交的事务事务已经提交
此时数据已经被 update
+—-+——+——+——+
| a | b | c | d |
+—-+——+——+——+
| 1 | 101 | 1 | 1 |
| 2 | 102 | 2 | 2 |
| 3 | 103 | 3 | 3 |
| 4 | 104 | 4 | 4 |
| 5 | 105 | 5 | 5 |
| 6 | 106 | 6 | 6 |
| 7 | 107 | 7 | 7 |
| 8 | 108 | 8 | 8 |
| 9 | 109 | 9 | 9 |
| 10 | 110 | 10 | 10 |
+—-+——+——+——+

innodb_force_recovery =6 不执行前滚操作，但是恢复的时候有回滚操作
+—-+——+——+——+
| a | b | c | d |
+—-+——+——+——+
| 1 | 101 | 1 | 1 |
| 2 | 102 | 2 | 2 |
| 3 | 103 | 3 | 3 |
| 4 | 104 | 4 | 4 |
| 5 | 105 | 5 | 5 |
| 6 | 106 | 6 | 6 |
| 7 | 107 | 7 | 7 |
| 8 | 108 | 8 | 8 |
| 9 | 109 | 9 | 9 |
| 10 | 110 | 10 | 10 |
+—-+——+——+——+

130626 16:44:29 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
InnoDB: Doing recovery: scanned up to log sequence number 0 8680656
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 9999 row operations to undo
InnoDB: Trx id counter is 0 14080
InnoDB: Last MySQL binlog file position 0 920753, file name /vobiledata/mysqllog/mysql-bin.000245
InnoDB: Starting in background the rollback of uncommitted transactions
130626 16:44:29 InnoDB: Rolling back trx with id 0 13057, 9999 rows to undo

InnoDB: Progress in percents: 1130626 16:44:29 InnoDB: Started; log sequence number 0 8680656
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79130626 16:44:29 [Note] Event Scheduler: Loaded 0 events
130626 16:44:29 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.1.57-log’ socket: ‘/tmp/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 0 13057 completed
130626 16:44:29 InnoDB: Rollback of non-prepared transactions completed
130626 16:45:08 mysqld_safe Starting mysqld daemon with databases from /vobiledata/mysqldata
130626 16:45:08 [Note] Plugin ‘FEDERATED’ is disabled.
130626 16:45:08 InnoDB: Initializing buffer pool, size = 2.0G
130626 16:45:08 InnoDB: Completed initialization of buffer pool
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
130626 16:45:08 InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
130626 16:45:08 [Note] Recovering after a crash using /vobiledata/mysqllog/mysql-bin
130626 16:45:08 [Note] Starting crash recovery…
130626 16:45:08 [Note] Crash recovery finished.
130626 16:45:08 [Note] Event Scheduler: Loaded 0 events
130626 16:45:08 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.1.57-log’ socket: ‘/tmp/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
130626 16:45:14 InnoDB: error: space object of table test/test,
InnoDB: space id 3 did not exist in memory. Retrying an open.

-+——+——+——+
| 1 | 101 | 1 | 1 |
| 2 | 102 | 2 | 2 |
| 3 | 103 | 3 | 3 |
| 4 | 104 | 4 | 4 |
| 5 | 105 | 5 | 5 |
| 6 | 106 | 6 | 6 |
| 7 | 107 | 7 | 7 |
| 8 | 108 | 8 | 8 |
| 9 | 109 | 9 | 9 |
| 10 | 110 | 10 | 10 |
+—-+——+——+——+

130626 16:44:29 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
InnoDB: Doing recovery: scanned up to log sequence number 0 8680656
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 9999 row operations to undo
InnoDB: Trx id counter is 0 14080
InnoDB: Last MySQL binlog file position 0 920753, file name /vobiledata/mysqllog/mysql-bin.000245
InnoDB: Starting in background the rollback of uncommitted transactions
130626 16:44:29 InnoDB: Rolling back trx with id 0 13057, 9999 rows to undo

InnoDB: Progress in percents: 1130626 16:44:29 InnoDB: Started; log sequence number 0 8680656
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79130626 16:44:29 [Note] Event Scheduler: Loaded 0 events
130626 16:44:29 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.1.57-log’ socket: ‘/tmp/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 0 13057 completed
130626 16:44:29 InnoDB: Rollback of non-prepared transactions completed
130626 16:45:08 mysqld_safe Starting mysqld daemon with databases from /vobiledata/mysqldata
130626 16:45:08 [Note] Plugin ‘FEDERATED’ is disabled.
130626 16:45:08 InnoDB: Initializing buffer pool, size = 2.0G
130626 16:45:08 InnoDB: Completed initialization of buffer pool
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
130626 16:45:08 InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
130626 16:45:08 [Note] Recovering after a crash using /vobiledata/mysqllog/mysql-bin
130626 16:45:08 [Note] Starting crash recovery…
130626 16:45:08 [Note] Crash recovery finished.
130626 16:45:08 [Note] Event Scheduler: Loaded 0 events
130626 16:45:08 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.1.57-log’ socket: ‘/tmp/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
130626 16:45:14 InnoDB: error: space object of table test/test,
InnoDB: space id 3 did not exist in memory. Retrying an open.