Showing all 5 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
37987 | 2008-07-09 11:30 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Duplicate (5448 days) | S3 | 5.0.58 | Any | Any | shutdown hangs after server was started with innodb_force_recovery set |
46193 | 2009-07-15 7:28 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5032 days) | S1 | >=5.1.31, 5.1.37, 5.1.42, 5.4.4 | Any (win xp, fc8) | Any | crash when accessing tables after enabling innodb_force_recovery option |
55832 | 2010-08-09 6:32 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4866 days) | S1 | 5.1.49, 5.5.5 | Any | Any | selects crash too easily when innodb_force_recovery>3 |
71552 | 2014-02-01 16:19 | 2014-07-21 16:08 | MySQL Server: Documentation | Closed (3538 days) | S3 | 5.6 | Any | Any | Manual is somewhat wrong/incomplete for innodb_force_recovery |
83255 | 2016-10-04 16:02 | 2017-05-04 7:47 | MySQL Server: InnoDB storage engine | Verified (2520 days) | S2 | any, 5.7.15 | Any | Any | --innodb-force-recovery=6 possibly corrupts doublewrite buffer |
Showing all 5 (Edit, Save, CSV, Feed) |