[mythtv-commits] Ticket #7936: MythTV is expiring just recorded recordings instead of older recordings

MythTV mythtv at cvs.mythtv.org
Sun Aug 29 05:15:49 UTC 2010


#7936: MythTV is expiring just recorded recordings instead of older recordings
----------------------------------------------------+-----------------------
 Reporter:  Jonathan Martens <jonathan@…>           |           Owner:  mdean     
     Type:  defect                                  |          Status:  assigned  
 Priority:  minor                                   |       Milestone:  0.24      
Component:  MythTV - General                        |         Version:  0.22-fixes
 Severity:  medium                                  |      Resolution:            
 Keywords:                                          |   Ticket locked:  0         
----------------------------------------------------+-----------------------
Changes (by mdean):

  * priority:  major => minor
  * severity:  high => medium


Comment:

 Jonathan, your log extract in comment:8 shows a list being built, but no
 shows being expired.  Do you still have the full log from that run that
 you referenced?  If not, I'll need to see a new, complete, -v file log
 showing the list being built and an incorrect/out-of-order recording being
 expired.

 On first glance, though, it looks like your "just recorded" recordings may
 be marked as Watched while all your old recordings that are being expired
 later are not marked as Watched.  You have enabled, "Watched before
 UNwatched: If set, programs that have been marked as watched will be
 expired before programs that have not been watched.", so new programs that
 have been watched will be expired before old programs that have not--with
 priority and starttime being secondary and tertiary sort criteria.

 Nick, your description in comment:13 sounds like the shows that are higher
 in auto-expire priority order all exist on file systems (and/or hosts)
 other than the file system that's in use.  Based on your specified
 configuration, it's sounds like the master backend can see recordings
 created by the remote backend.  Can you please find out if in one of the
 cases where recordings seem to be expired out-of-order any of the
 recordings that are skipped are "owned" by the other backend (not the one
 that's recording) but exist on the file system to which this backend is
 recording?

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7936#comment:18>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list