[mythtv-users] Help! - Mythtv is expiring the wrong recordings

[David Brodbeck]

On Mon, September 22, 2008 2:17 pm, Joe Ripley wrote:
> On Mon, Sep 22, 2008 at 12:56 PM, Yeechang Lee <ylee at pobox.com> wrote:
>> Nick Craig-Wood <nick at craig-wood.com> says:
>>> I reset the flag with "update recorded set deletepending=0 where
>>> deletepending !=0;" and the --printexpire now looks sensible.
>>
>> Thanks for the tip. I ran
>>
>>       select * from recorded where deletepending != 0;
>>
>> and found four recordings with the flag, which I changed with your
>> above command. I agree that some failed delete thread is likely the
>> cause.
>>
>> I suggest that anyone whose mythbackend has ever crashed (which is
>> about 99.44% of us) searches and, if necessary, corrects for the
>> flag. Perhaps this could go into optimize_mythdb.pl?
>
> I guess I'm one of the lucky ones:
>
> select * from recorded where deletepending != 0;
> Empty set (0.00 sec)

I found two.  One is for a file that no longer exists.  The other is a
file that exists, but is obviously truncated (only 22M) and doesn't show
up in the recorded programs list.  Is it safe to delete the file?

BTW, I'm not using slow deletes.