MySQL Bugs: #54760: mysql loss data after server outage

Bug #54760	mysql loss data after server outage
Submitted:	24 Jun 2010 1:31	Modified:	26 Jul 2010 11:09
Reporter:	dennis zeng	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.1.41	OS:	Linux (Ubuntu10.4)
Assigned to:		CPU Architecture:	Any
Tags:	mysql loss data after server outage

Description:
I used mysql with JIRA, and I add several issues in JIRA yesterday, and all the function worked well, after server outage, I found all the issues I inputed yesterday were disappeared.
I think it might because that mysql cache the records in memory after server outage, all the data lost, is there any means to recover these records from mysql ?

How to repeat:
add records into mysql, and then make the server outage. After that all the records added today will loss

What exact version, 5.x.y, do you use? Please, upload error log of your MySQL server. Usually it is <hostname>.err in the data directory.

Where is the exact path of the log file in ubuntu ?

If you installed from .deb, I assume messages are logged to the usual OS location, /var/log/messages likely.

I checked it
100623 23:14:26 [Note] Plugin 'FEDERATED' is disabled.
100623 23:14:26  InnoDB: Started; log sequence number 0 44233
100623 23:14:29 [Note] Event Scheduler: Loaded 0 events
100623 23:14:29 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12.3'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/OS_CURRENTSTEP' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/OS_CURRENTSTEP'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/OS_WFENTRY' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/OS_WFENTRY'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/SEQUENCE_VALUE_ITEM' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/SEQUENCE_VALUE_ITEM'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/component' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/component'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/jiraissue' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/jiraissue'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/nodeassociation' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/nodeassociation'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/notificationinstance' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/notificationinstance'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/project' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/project'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/projectroleactor' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/projectroleactor'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/propertystring' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/propertystring'
100623 23:14:37 [ERROR] /usr/sbin/mysqld: Table './jiradb/userhistoryitem' is marked as crashed and should be repaired
100623 23:14:37 [Warning] Checking table:   './jiradb/userhistoryitem'

So, had you tried to repair all that (MyISAM?) tables, as suggested? Check http://dev.mysql.com/doc/refman/5.1/en/repair-table.html for possible options.

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".