Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.8
-
10.1.11, 10.1.14
Description
Innodb force recovery settings prevent its own recovery. In innodb_force_recovery=6 and read only mode, no reason to expect change or doublewrite buffers to be empty. It does however complain about the change buffer not being empty:
[ERROR] InnoDB: Change buffer must be empty when --innodb-read-only is set!
Same bug in MySQL:
https://bugs.mysql.com/bug.php?id=77476
Attachments
Issue Links
- relates to
-
MDEV-8963 innodb_force_recovery >= 4 won't work
-
- Closed
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Remote Link | This issue links to "Bug #77476 innodb_force_recovery = 6 cannot recover ANY DATA when change buffer not empty (Web Link)" [ 25718 ] |
Fix Version/s | 10.1 [ 16100 ] | |
Assignee | Jan Lindström [ jplindst ] | |
Labels | upstream |
Sprint | 10.1.11 [ 30 ] |
Rank | Ranked lower |
Status | Open [ 1 ] | In Progress [ 3 ] |
Sprint | 10.1.11 [ 30 ] | 10.1.11, 10.1.14 [ 30, 51 ] |
Rank | Ranked lower |
issue.field.resolutiondate | 2016-04-27 08:12:25.0 | 2016-04-27 08:12:25.274 |
Component/s | Storage Engine - InnoDB [ 10129 ] | |
Fix Version/s | 10.1.14 [ 21804 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 72527 ] | MariaDB v4 [ 149817 ] |