Opened 12 years ago

Closed 12 years ago

#6742 closed defect (invalid)

autoexpire list inaccurate and results in unwanted deletions.

Reported by: chuck.peters+mythbug@… Owned by: Isaac Richards
Priority: major Milestone: unknown
Component: MythTV - General Version: 0.21-fixes
Severity: medium Keywords:
Cc: Ticket locked: no


mythbackend --printexpire is shown below. If accurate I would expect the Billiards program won't be deleted until all the Hardball's and Charlie Rose's shows are expired... But that's not what always happens.

My Default Storage Group has 5 directories, each on its own disk. Then new recordings are randomly started on one of the various 5 disks and something gets deleted on that particular disk. ie I have seen the Billiards get deleted long before the Hardball.

For the autoexpire list to be accurate we need a function of what disk the recordings are on. ie In the frontend and mythweb interfaces we need to be able to sort by disk and then sort by recording priority, date etc...

MythTV AutoExpire List (programs listed in order of expiration)
Hardball With Chris Matthews             2224MB  Mon Jun 15 17:00:00 2009 [-13]
Hardball With Chris Matthews             2224MB  Tue Jun 16 17:00:00 2009 [-13]
Hardball With Chris Matthews             2225MB  Wed Jun 17 17:00:00 2009 [-13]
Hardball With Chris Matthews             2225MB  Wed Jun 24 17:00:00 2009 [-13]
Charlie Rose                             2226MB  Sat Jun 20 00:00:00 2009 [ -5]
Charlie Rose                             2225MB  Wed Jun 24 00:30:00 2009 [ -5]
Charlie Rose                             2226MB  Thu Jun 25 00:00:00 2009 [ -5]
Billiards: "1998 WPBA Classic Tour, Fir  1125MB  Tue Jul 7 10:00:00 2009  [ -2]
Billiards: "World Cup of Trick Shots, S  1125MB  Tue Jul 7 19:30:00 2009  [ -2]

Change History (1)

comment:1 Changed 12 years ago by cpinkham

Resolution: invalid
Status: newclosed

There is no way that we can know the exact order in which files will be expired because we do not know exactly where new recordings will be placed in the future. This is based on things outside of the AutoExpirer?'s knowledge or control such as what files will be deleted in the meantime, what programs will be recorded in the meantime, what additional non-Myth fileswill be put on the filesystems, etc..

[21221] modified the Storage Scheduler to add a new balancing method called "Balanced Free Space" to fill up drives based on free space. In [21225], I applied a patch from another user that modified the Storage Scheduler to take another scheduling pass when all drives are full and something will have to be AutoExpired? to make room for the new recording. This additional scheduling pass looks at what files may be AutoExpired? in order to make room for the new recording and places the new recording on the best filesystem based on what is at the beginning of the AutoExpire? list.

I'm not sure how much more we can do to this. For now, I'm closing this as a Feature Request without a patch. If you or someone else would like to make a patch to try to make this more accurate, please bring the subject up in the IRC channel or on the mailing list.

Note: See TracTickets for help on using tickets.