Jesse wrote: > > Dan Wilga wrote: > >> I've been running with InnoDB for the last year; IMHO more > reliable > >> in case of system crashes where MyISAM tables tend to corrupt more > >> easily (esp. recordmarkup). > > > > I run a high-volume web site that uses MySQL for some > pretty frequent > > tasks, and haven't had any data corruption problems. > > I found my problem, but I'm not sure how to fix it. Every > sunday morning > I shut down my > MySQL database and analyze and repair all tables. This is a trick I > learned from my production > Sys Admin days with MySQL versions 3.23.x. > > Unfortunately, it looks like the Gentoo /etc/init.d/mysql > doesn't shut > down the database properly. > So I get errors. Ugh. Oh well, INNODB won't solve that. I > just need to > fix the shutdown proceedure > I guess.
Not quite the same but I suffer every now and then (well twice anyway) with a corrupted recordedmarkup table[1], I suspect from the few times the machine has hard locked and I've had to power off[2], as a quick future fix if it happens again I added a few lines to the mysql startup script to touch a file on startup and remove it on (clean) shutdown. Then a little section to run myisamchk -f on all the *.MYI files if the flag is there on startup. Even if it has to run still takes only a second or so to run and hopefully should prevent any reoccurances of corruption. HTH David [1] Symptoms for anyone searching for a fix to their problem: No pictures in recorded programs on mythweb Skippy fast forward/rewind Unable to correctly display the clip length/total time keeps changing. No error messages as my logs have rotated too many times since the last time. [2] Not noticed until well after the event the first time and spent ages trying to work out what went wrong, noticed 3 days the second time and was able to tie it down to when the machine locked.
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
