Bug #56023 Table got corrupted and server kept crashing
Submitted: 16 Aug 2010 17:36 Modified: 16 Aug 2010 18:05
Reporter: Jamie Ma Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: General Severity:S1 (Critical)
Version:5.1.37 OS:Linux (Ubuntu 8.04)
Assigned to: CPU Architecture:Any
Tags: corrupted;crash;

[16 Aug 2010 17:36] Jamie Ma
Description:
We have a Linux Ubuntu system which has Mysql server 5.1.37 installed. The database uses the InnoDB engine.

On one customer site, our application's connection to Mysql server was cut off very often. We found out eventually one of the tables was corrupted. We could select the first few and the last few rows, but as soon as our query touched the few hundreds of rows in the middle, we would experience Mysql server crash 100% of time. We cannot dump the content of this table since it crashed in the middle. We had to delete this table and rebuild it. The problem was solved and we haven't experienced any crash afterwards.

Since it's a production system on customer site, we had to fix it right away. So we cannot reproduce this issue any more. We don't have any system log available, since we were notified days after the first crash happened. The only thing we have is Mysql error log.

How to repeat:
N/A
[16 Aug 2010 17:51] MySQL Verification Team
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.
[16 Aug 2010 18:02] Jamie Ma
Mysql error log

Attachment: mysql.err (application/octet-stream, text), 491.40 KiB.

[16 Aug 2010 18:05] Jamie Ma
We tried to restart Mysql and the system a couple of times. But it didn't solve the problem, until we rebuilt the corrupted table.