RE: [mythtv-users] MySQL: INNODB?
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 mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MySQL: INNODB?
At 4:45 PM -0400 10/3/05, Jesse Guardiani wrote: 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. I don't find that this is necessary with 4.1.x. The web site works fine without it, and on my Myth box I've never had any corruption despite the machine needing lots of unclean reboots. It probably is a good idea to periodically (like, once a month) *optimize* the tables Myth uses. All those adds and deletes can make space usage and table indexes really inefficient. -- Dan Wilga [EMAIL PROTECTED] Web Administrator http://www.mtholyoke.edu Mount Holyoke CollegeTel: 413-538-3027 South Hadley, MA 01075Who left the cake out in the rain? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MySQL: INNODB?
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. The thing to remember about MyISAM tables is that they are, at their lowest level, Berkeley DB files. (See http://sleepycat.com). You will have problems with BDB files if they are not stored on the machine running MySQL (i.e.: they are accessed by NFS or the like.) MySQL also has some pretty cool replication features, which I use to back up all of my site's data to two other machines in real time. It's a pain to set up, but works pretty well once it's turned on. -- Dan Wilga [EMAIL PROTECTED] Web Administrator http://www.mtholyoke.edu Mount Holyoke CollegeTel: 413-538-3027 South Hadley, MA 01075Who left the cake out in the rain? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MySQL: INNODB?
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. -- Jesse Guardiani Programmer/Sys Admin [EMAIL PROTECTED] ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MySQL: INNODB?
On 02/10/05, Jesse Guardiani [EMAIL PROTECTED] wrote: Hello, Has anyone tried running MythTV with INNODB tables? I run them at work, and they seem very reliable. MyISAM, on the other hand, seems to corrupt easily. At least once a month I have to fix a table... Is INNODB a drop in replacement? 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've not experienced any problems so far. N. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
