myisam_recover fails to auto-repair all tables

Bug #819348 reported by Dreas van Donselaar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MariaDB
Fix Released
High
Michael Widenius

Bug Description

We're running MariaDB with in my.cnf "myisam_recover = BACKUP_ALL,FORCE". We regularly have a crashed table on servers that fail to auto-repair:
===
Aug 1 06:19:07 mx10 mysqld: 110801 6:19:07 [ERROR] mysqld: Table './database/test@002dtable' is marked as crashed and should be repaired
Aug 1 06:19:07 mx10 mysqld: 110801 6:19:07 [Warning] Checking table: './database/test@002dtable'
Aug 1 06:24:22 mx10 mysqld: 110801 6:24:22 [Warning] Recovering table: './database/test@002dtable'
Aug 1 06:24:36 mx10 mysqld: 110801 6:24:36 [Note] Retrying repair of: './database/test@002dtable' with keycache
Aug 1 06:24:36 mx10 mysqld: 110801 6:24:36 [ERROR] Couldn't repair table: mx_messages.test-table
Aug 1 06:24:36 mx10 mysqld: 110801 6:24:36 [ERROR] mysqld: Table './database/test@002dtable' is marked as crashed and last (automatic?) repair failed
===

We have no problems manually repairing the table with "REPAIR tablename". Log collection/a copy of such broken table has been reported some weeks ago already via the MariaDB FTP server and was picked up by Monty. Just never created an official ticket for it.

Changed in maria:
assignee: nobody → Michael Widenius (monty)
milestone: none → 5.2
Revision history for this message
Michael Widenius (monty) wrote :

Already fixed in MariaDB 5.2 some months ago

Changed in maria:
importance: Undecided → High
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.