[mythtv-users] './mythconverg/recordedseek' is marked as crashed

Bill Meek keemllib at gmail.com
Wed Jul 29 02:55:17 UTC 2015


On 07/28/2015 09:21 PM, Hika van den Hoven wrote:
> Hoi Hika,
>
> Wednesday, July 29, 2015, 3:50:46 AM, you wrote:
>
>> Hoi All,
>
>> It seems my recordedseek table is crashed. What do I do now?
>> Backups return empty and optimize_mythdb.pl fails.
>> It seems to have happened a few days ago since the last backup with
>> content was from almost a week ago.
>> For the rest everything works. I can record, watch, schedule. That's
>> why I didn't notice at first.
>
>> I guess I somehow have to dump the table and recreate it. Which will
>> take a long time. (some 3.4 Tb in recordings )
>
> OK, now it gets really weird. It seems that optimize_mythdb.pl crashes
> the table.
> I emptied the table.
> Restarted mysql end mythbackend
> I could see the table again.
> Rebuilding a recording works.
> I could do a backup again.
> And then just to be sure I ran optimize_mythdb.pl and I'm back where I
> started. "last repair failed at optimize_mythdb.pl line 38"
>
> So I'm doing it again and for now remove optimize_mythdb.pl from cron.
>

Isn't line 38 the 'new' "ALTER TABLE recordedseek ORDER BY chanid, starttime, type"
code? You could temporarily comment out that part just to prove it is/isn't causing
the problem.

-- 
Bill


More information about the mythtv-users mailing list