[mythtv-users] Strange seeking following database crash
Michael T. Dean
mtdean at thirdcontact.com
Mon Jan 21 18:47:53 UTC 2013
On 01/21/2013 10:36 AM, Ian Oliver wrote:
> Due to a power cut, we had quite a large database crash, which I
> repaired with
>
> mysqlcheck --auto-repair --check - u xxxxx -p mythconverg
>
> All seems well, but the database is now half the size it was and some
> programmes have odd seeking behaviour.
>
> We don't use commercial seek but do use the skip forward/back all the
> time with settings of +30 seconds and -7 seconds. Backwards now often
> goes back to the same place in some recordings, which can be minutes
> earlier.
>
> Do I just need to follow the instructions for repairing a corrupted
> seek table?
Yes. Just run mythcommflag --rebuild on each affected recording--or, if
you prefer, on every single recording (and then wait a few days for
things to go back to normal).
Then, the 2nd thing you need to do is:
http://www.mythtv.org/wiki/Database_Backup_and_Restore (specifically the
part at
http://www.mythtv.org/wiki/Database_Backup_and_Restore#Automating_Database_Backups
). :)
Mike
More information about the mythtv-users
mailing list