maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: MariaDB loop with MyISAM tables marked as crashed
CREATION DATE..: Fri, 08 Oct 2010, 19:54
SUPERVISOR.....: 
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Server-RawIdeaBin
TASK ID........: 155 (http://askmonty.org/worklog/?tid=155)
VERSION........: WorkLog-4.0
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:



DESCRIPTION:

On several servers (3) MariaDB 5.1 crashed after an upgrade from from MySQL 5.0. 
Log shows:
===
Version: '5.1.50-MariaDB-mariadb84-log'  socket: '/var/run/mysqld/mysqld.sock'  
port: 3306  (MariaDB - http://mariadb.com/)
101008 14:35:17 [ERROR] mysqld: Table './database123/table123' is marked as 
crashed and should be repaired
101008 14:35:17 [Warning] Checking table:   './database123/table123'
101008 14:35:17 mysqld_safe Number of processes running now: 0
101008 14:35:17 mysqld_safe mysqld restarted
===

This is looping, so things only get worse every time with more crashed tables. 
Using myisamchk to repair all MYI tables actually "fixes" the issue, but I guess 
it can come back after an unclean shutdown. This appears to be a major bug. I have 
a copy of such corrupt database available on request (information is 
confidential).


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v4.0.0)