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

Nick Craig-Wood nick at craig-wood.com
Mon Sep 22 14:58:07 UTC 2008


Jon Bishop <jon.the.wise.gdrive at gmail.com> wrote:
> 
>  On Sep 22, 2008, at 4:04 AM, Nick Craig-Wood wrote:
> 
> > I've just noticed that mythv (0.20.2.svn20071021-0.2) has started
> > expiring the wrong recordings.
> > <snip>
> > However "mythbackend --printexpire" only shows stuff recorded recently
> > which is the problem I guess.
> > <snip>
> > Any ideas what might have happened or what I could check?
> 
>  Seeing that you're using .20.2, and not .21, you don't use recording  
>  groups,

Correct

>  which would have been my first guess. My second guess is that  
>  you are expiring based on priority and not record date. It's a setting  
>  in the frontend somewhere. Check that. If you are, then you will need  
>  to increase the priority of the shows you want to preserve.

It is a good thought, but I just checked and it is set to expire
"Oldest first".

After using "mythbackend -v all --printexpire" and trying all the sql
by hand I eventually worked out that all the old recordings had the
deletepending flag set.

I reset the flag with "update recorded set deletepending=0 where
deletepending !=0;" and the --printexpire now looks sensible.

As to why mythtv tried to delete all those things and failed there
isn't any clue in the logs.

Perhaps the delete thread crashed or something like that?

I've already restarted mythtv - I'll see if it does it again!

-- 
Nick Craig-Wood <nick at craig-wood.com> -- http://www.craig-wood.com/nick


More information about the mythtv-users mailing list