[mythtv-users] Lost Recording - Autoexpire Woes?

[Michael T. Dean]

On 07/11/2012 04:24 PM, David Watkins wrote:
> Could someone please confirm whether or not the last line of the
> backend log snippet below means that my recording of "Twenty Twelve",
> from last night, was autoexpired this evening for space reasons?  The
> combined backend/frontend machine had been turned on for about 5
> minutes, and no recordings had started or been added to the schedule
> before the following happened:
>
>
> 2012-07-11 20:09:25.879629 I [1753/1953] Scheduler scheduler.cpp:2069
> (HandleReschedule) - Scheduled 147 items in 1.9 = 0.00 match + 1.91
> place
> 2012-07-11 20:11:54.326259 I [1753/1955] HouseKeeping
> housekeeper.cpp:225 (RunHouseKeeping) - Running housekeeping thread
> 2012-07-11 20:16:54.333285 I [1753/1955] HouseKeeping
> housekeeper.cpp:225 (RunHouseKeeping) - Running housekeeping thread
> 2012-07-11 20:18:01.493247 N [1753/1956] Expire autoexpire.cpp:263
> (CalcParams) - AutoExpire: CalcParams(): Max required Free Space: 1.0
> GB w/freq: 15 min
> 2012-07-11 20:18:01.504122 N [1753/1956] Expire autoexpire.cpp:640
> (SendDeleteMessages) - Expiring 1811 MB for 1054 at
> 2012-07-10T21:59:00 =>  "Twenty Twelve":Catastrophisation
>
>
> Assuming that this is the case, can anyone explain why this might have
> happened when I have 674G available recording space?
>
> Disk Usage Summary:
> Total Disk Space:
> Total Space: 1,394,322 MB
> Space Used: 719,464 MB
> Space Free: 674,858 MB
> Space Available After Auto-expire: 1,094,806 MB
> Space Used by LiveTV: 0 MB
> Space Used by Deleted Recordings: 0 MB
> Space Used by Auto-expirable Recordings: 419,948 MB
>
> and what I can do to prevent it happening again.
>
> I'm off to look at line 640 of autoexpire.cpp, but not being a
> programmer, I'm not very hopeful of being able to learn much.
>
> Thanks
>
>
> running 0.25 fixes from a few weeks ago
>
>
> MythTV Version : v0.25-61-gd064338-dirty
> MythTV Branch : fixes/0.25
> Network Protocol : 72
> Library API : 0.25.20120408-1
> QT Version : 4.7.4
>
>
> (Not sure about the -dirty suffix, but could be because I've applied a
> couple of mythmusic patches?)

That's a 2-mo old revision (from May 1) that was before a fix (pushed 
about 20 days later than your revision) that was made for the backend's 
expiring things it shouldn't.  I can't guarantee that updating will fix 
the problem you encountered, but you should definitely update.

That said, did you just upgrade your mythtv from 0.24?  If so, let me 
know and I can probably tell you what actually happened (no one should 
upgrade to 0.25 using a revision from before May 16).

Mike