Check your database, you may have corrupted tables and/or indexes on tables. Alternatively your database partition may be full (preventing writes), which amounts to the same problem. I have experienced problems like this after mysql got itself messed up due to partition full or machine crash, In my case the db was suffering from inability to write metadata for recordings, which is why the time data was all off.
<br><br>Below are the notes I wrote for myself for repairing a broken database. Check them before using yourself, and of course your mileage may vary :-) There is much documentation on myisamchk at the mysql website.<br><br>
If this is your problem, then after repairing tables the recordings with messed up time info will still
have messed up time info, but at least new recordings will get correct
time info.<br><br>Recovery of MYSQL after /var/ filled up.<br><br>1) Make sure mysql is shut down.<br><br>2) Clear some space on /var - i.e. resolve the issue.<br><br>3) Run 'myisamchk *.MYI' to see if tables are corrupted. Databases are in subdir
<br>ectories under /var/lib/mysql. Remember to check/repair ALL databases, not just<br>'mythconverg' or 'mysql'. Use --silent to just see errors and not have loads of<br>debug output.<br><br>4) Run 'myisamchk --recover *.MYI' to repair tables and rebuild indexes. Can take a binary copy of the tables first if desired.
<br><br>5) Check tables again as per step 3, using --silent. Hope to see no messages.<br><br>6) If all well, restart mysql.<br><br><br><br><br><div><span class="gmail_quote">On 11/15/06, <b class="gmail_sendername">Marco Nelissen
</b> <<a href="mailto:marcone@xs4all.nl">marcone@xs4all.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">>On 11/14/06, Justin Hornsby <
<a href="mailto:justin.hornsby@gmail.com">justin.hornsby@gmail.com</a>> wrote:<br>>> On 15/11/06, Marco Nelissen <<a href="mailto:marcone@xs4all.nl">marcone@xs4all.nl</a>> wrote:<br>>> > I have this recording that is about an hour long, however mythtv thinks
<br>>> > it's 2 minutes and 31 seconds. As a result, skipping forward and backward<br>>> > is... interesting.<br>>> > I tried rebuilding the seektable with mythcommflag, but it had no effect.<br>
>> > How can I convince mythtv that this recording is in fact 1 hour long?<br>>><br>>> Is your machine set to use the right timezone?<br>><br>>Or if you are using separate fe and be, are their times in sync?
<br><br>This is a combined FE/BE, and the timezone is set correctly. Why would<br>a wrong timezone even make mythtv confused about the duration of this<br>recording? I can see how it would cause recordings to happen at the
<br>wrong time, but why would it make mythtv think that this 1-hour recording<br>is a 2-and-a-half minute recording?<br><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">
mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>