[mythtv-users] Mysql complains at me

shadestalker@gmail.com shadestalker at gmail.com
Thu Jan 26 21:00:54 UTC 2006


On 1/26/06, Ryan Rawson <ryan at invasioncity.com> wrote:
>
> So I had to powercycle the computer that runs mythtv.  Luckly my
> filesystem is journaled (ext3 and xfs) so I didn't have to wait long,
> but wait, surprise for me in my mailbox:
>
> Subject: WARNING: mysqlcheck has found corrupt tables
>
> The debian packaging of mysql runs check tools on system boot.
>
> So apparently my mythtv tables may or may not be corrupt.  The rest
> of the message just indicates that some tables weren't closed
> correctly, and now people are accessing them.
>
> Now I don't really want advice how to fix this, since I don't have
> the time or interest to fix it (and I'm getting rid of cable
> anyways).  But I'd like to say that as a power-user who just wants to
> be an end user, this is a very bad experience.  The one instruction
> for fixing it involves like 10 steps.  I'm not really interested in
> this, I'm really interested in watching my TV, not databases.
>
> My engineering hat comes on, and says - this is intolerable.  Mysql
> isn't really helping here, and maybe mythtv should at LEAST offer the
> option of using a database that doesn't need care and feeding after
> system crashes/hard reboots.  My prime vote would be for postgresql.
>
> At this point I cannot really recommend mythtv to anything less than
> a power developer.  Fixing corrupt mysql tables is NOT cool and not
> at all interesting.



I don't think it's been suggested by anyone who's given it real thought that
mythtv is meant for anyone unwilling to get their hands dirty, both in the
initial setup and occasionally thereafter doing maintenance.

You're certainly right to not recommend mythtv to mom and pop, but slamming
the policy of the system to leave system administration up to the system
administrator is out of place, IMO.  You're perfectly welcome to write your
own init script that checks for problems with the database and simply drops
and rebuilds any tables that are suspect, however I think most end-users and
certainly most mythtv DIY people wouldn't want that outcome.  In the end,
your mythtv is what *you* make of it (or don't).

I still haven't setup regular backups of my db, so I'm inviting exactly the
above situation on myself.  I acknowledge the possibility and responsibility
I have to deal with it if it does happen, but the fact that mythtv is that
way means I won't ever build one and send it to my mom.  It's bad enough she
has a DVD player.  ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060126/e0b3b5d8/attachment.htm


More information about the mythtv-users mailing list