[MDEV-3105] LP:819348 - myisam_recover fails to auto-repair all tables Created: 2011-08-01  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Dreas van Donselaar (Inactive) Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug819348.xml    

 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.



 Comments   
Comment by Michael Widenius [ 2011-11-07 ]

Re: myisam_recover fails to auto-repair all tables
Already fixed in MariaDB 5.2 some months ago

Comment by Rasmus Johansson (Inactive) [ 2011-11-07 ]

Launchpad bug id: 819348

Generated at Thu Feb 08 06:46:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.