[mythtv] [mythtv-commits] Ticket #5746: With multiple disk of different sizes, place new recording on partition which will have the lowest priority files deleted
ylee at pobox.com
Sun Sep 28 18:41:45 UTC 2008
John Fulton <john at geode.homelinux.org> says:
> What annoyed me the most was that the auto-expire list under the
> system information menu gave no hint that this was going to occur.
> So I looked into it and this patch is the result.
Indeed. That the current auto-expire list is (often wildly) inaccurate
is clearly a bug, and potentially a very serious one (as you and
others found during the Olympics).
> The patch doesn't take into consideration multiple simultaneously
> recordings, so it may get the ordering slightly wrong but no where
> near as bad as not having it.
As you note, the stated auto-expire ordering as it currently stands
isn't completely accurate even with your patch but it's surely a huge
I still hold to what I stated in the referenced thread: The default
ought to be MythTV able to record to any available
directory--regardless of how many simultaneous recording or playback
streams are occurring, or whether it is local or remote--with the only
default criteria for selection being whichever directory has the
first-on-the-list expirable programs that will create enough room for
the recording to be saved into.
If someone wants to tweak the behavior with the storage-group
weightings to take into account local versus remote directories, or
the number of simultaneous streams, the onus should be on him. Not the
new-to-MythTV user who attaches a new home NAS to his network and then
is mystified by why recordings made just an hour ago are being expired
despite all the new empty space.
I will report any odd behavior I see but thanks for addressing a
yawning need. Speaking of storage-group weights, how does your patch
account for them, if any?
Yeechang Lee <ylee at pobox.com> | San Francisco CA US
More information about the mythtv-dev