MariaDB loop with MyISAM tables marked as crashed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
New
|
Undecided
|
Unassigned |
Bug Description
On several servers (3) MariaDB 5.1 crashed after an upgrade from from MySQL 5.0.
Log shows:
===
Version: '5.1.50-
port: 3306 (MariaDB - http://
101008 14:35:17 [ERROR] mysqld: Table './database123/
crashed and should be repaired
101008 14:35:17 [Warning] Checking table: './database123/
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. (see WL#155)
Changed in maria: | |
milestone: | none → 5.1 |
Monty found that this occurred because thread_stack was set to 128K instead of 256K which is required for MariaDB 5.1. Still seems that should be fixed though (or at least MariaDB should refuse to start with a clear error message).