MySQL Bugs: #55756: MySQL repeat restart itself with error

Bug #55756	MySQL repeat restart itself with error
Submitted:	5 Aug 2010 3:23	Modified:	5 Sep 2010 9:39
Reporter:	Thammasak Nimit	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	Server version: 5.0.45-community	OS:	Linux (Redhat AS 4 update 4)
Assigned to:		CPU Architecture:	Any

Description:
100805 7:28:53 [ERROR] /usr/sbin/mysqld: Table '' is marked as crashed and should be repaired
100805 7:28:53 [ERROR] /usr/sbin/mysqld: Sort aborted
100805 7:28:58 [ERROR] /usr/sbin/mysqld: Table '' is marked as crashed and should be repaired
100805 7:28:58 [ERROR] /usr/sbin/mysqld: Sort aborted
100805 7:30:16 [ERROR] /usr/sbin/mysqld: Table '' is marked as crashed and should be repaired
100805 7:30:16 [ERROR] /usr/sbin/mysqld: Sort aborted
100805 7:32:07 [ERROR] /usr/sbin/mysqld: Table '' is marked as crashed and should be repaired
100805 7:32:07 [ERROR] /usr/sbin/mysqld: Sort aborted
100805 7:33:03 InnoDB: Error: Write to file /mysql_data/ibdata1 failed at offset 0 1947779072.
InnoDB: 196608 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 5.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
100805 7:33:03InnoDB: Assertion failure in thread 1833384880 in file os0file.c line 4012
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
100805 7:33:03 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=4194304
read_buffer_size=4190208
max_used_connections=221
max_connections=220
threads_connected=220
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2706574 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

I'm checking disk space and qouta , it's ok. and I workaround by manual restart.

I hope you help fix this problem.

How to repeat:
-

Thank you for the report.

We are sorry, but we can not provide help on using our products in bug database designed to report bugs in MySQL code.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

In your case you should search user manual for InnoDB Froce recovery and check your disk where InnoDB tablespace is located.

But still is interesting why you get this error. At the same time you are using very old version. Please upgrade to current version 5.0.91 and inform us if you meet same problem again.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".