Innodb doesn't suffer from corruption issues nearly as often as myisam tables, and it is able to recover on its own in many cases (crash recovery.) In my experience, if innodb does get corrupted, it's most often because of hardware problems. You could consider using it instead.
From: Steve Staples [mailto:sstaples@stripped]
Sent: Monday, September 13, 2010 7:03 AM
Subject: Crashed Table - How to report/prevent?
Good day MySQL!
I had a table that crashed last night. There is a cron function that
goes out every 6 hours or so, that does a quick table backup (it's also
replicated, it's just something that we have running now). ANYWAY, I
think it crashed early in the evening, but when the backup ran, it looks
like it marked it as crashed finally (which was about 4 hours later).
The table was able to be read up until then, but it looks like it wasn't
able to be written too.
What I want to know is, is there a quick and easy way to maybe every few
hours, check to see if there are any crashed tables or whatnot?
This is only the 2nd time in the last 1 1/2 years. the table that
crashed, is a table that gets created every month, and is about 5gig in
size at the end of the month (it has a lot of records/fields in it which
is why i create a new one every month).
I could write a quick routine that goes and 'shows' the tables, and if
it fails, then repair it (or report it back to me via email or
Any ideas on a way to automate something that is efficient and quick?
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gtowey@stripped
This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you are notified that reviewing, disseminating, disclosing, copying or distributing this e-mail is strictly prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any loss or damage caused by viruses or errors or omissions in the contents of this message, which arise as a result of e-mail transmission. [FriendFinder Networks, Inc., 220 Humbolt court, Sunnyvale, CA 94089, USA, FriendFinder.com