Mailing List Archive: MythTV: Dev

Re: [mythtv-commits] Ticket #5746: With multiple disk of different sizes, place new recording on partition which will have the lowest priority files deleted

Index | Next | Previous | View Threaded

ylee at pobox

Sep 27, 2008, 10:28 PM

Post #1 of 5 (502 views)
Permalink

Re: [mythtv-commits] Ticket #5746: With multiple disk of different sizes, place new recording on partition which will have the lowest priority files deleted

mythtv <mythtv[at]cvs.mythtv.org> says:
> This patch adds a new pass to the placement algorithm which
> simulates expiring the old files in the users required order. When
> a partion is found with enough space that partition is selected for
> the new file.

I am rebuilding from source with the patch now and am looking forward
to trying the patch out. John, how effective have you found the patch
to deal with what the thread starting at
<URL:http://www.gossamer-threads.com/lists/mythtv/users/346903#346903>
discusses? In particular, does it take into account recordings placed
into the Deleted recording group for later auto-expiration?

--
Yeechang Lee <ylee[at]pobox.com> | San Francisco CA US
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

john at geode

Sep 28, 2008, 1:53 AM

Post #2 of 5 (475 views)
Permalink

Re: [mythtv-commits] Ticket #5746: With multiple disk of different sizes, place new recording on partition which will have the lowest priority files deleted [In reply to]

Yeechang Lee wrote:
> mythtv <mythtv[at]cvs.mythtv.org> says:
>
>> This patch adds a new pass to the placement algorithm which
>> simulates expiring the old files in the users required order. When
>> a partion is found with enough space that partition is selected for
>> the new file.
>>
>
> I am rebuilding from source with the patch now and am looking forward
> to trying the patch out. John, how effective have you found the patch
> to deal with what the thread starting at
> <URL:http://www.gossamer-threads.com/lists/mythtv/users/346903#346903>
> discusses? In particular, does it take into account recordings placed
> into the Deleted recording group for later auto-expiration
Some background: I discovered this bug during the Beijing games, my
system has two disks: 1 500 GB and 1 TB - There was just too much for me
to watch. After filling both disks the backend started auto-expiring
from the 500 G disk even though the programs were only 5 or 6 days old
and much older material (20 days) was on the 1TB disk. 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.

As to expiration order: I called GetAllExpiring(), the comments for
this function indicate that it should return the results in expiring
order. So I expect that deleted recordings would be expired first.

As to the thread: I note that some prefer the backend to chose the
local disks over network drives - this patch will only default to that
behaviour if it can't find some of the recordings to do the calculations
with.

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.

In case my system set up matters, I run both front and back end on the
same machine: Intel Core 2 duo running at 1.86 GHz, 1GB RAM, 3 dvb
tuners, I think 6 simultaneous recordings is my record.

Good luck with the rebuild.

Regards,
John
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

ylee at pobox

Sep 28, 2008, 11:41 AM

Post #3 of 5 (474 views)
Permalink

Re: [mythtv-commits] Ticket #5746: With multiple disk of different sizes, place new recording on partition which will have the lowest priority files deleted [In reply to]

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
improvement.

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
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

john at geode

Sep 28, 2008, 2:51 PM

Post #4 of 5 (470 views)
Permalink

Re: [mythtv-commits] Ticket #5746: With multiple disk of different sizes, place new recording on partition which will have the lowest priority files deleted [In reply to]

Yeechang Lee wrote:
> 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
If there is free space on all the drives. Pass 1 remains unchanged so
it will use the weights. Pass 2 which is what I added does not take them
into consideration.
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

ylee at pobox

Oct 11, 2008, 3:25 AM

Post #5 of 5 (287 views)
Permalink

Re: [mythtv-commits] Ticket #5746: With multiple disk of different sizes, place new recording on partition which will have the lowest priority files deleted [In reply to]

John Fulton <john[at]geode.homelinux.org> says:
> Pass 2 which is what I added does not take them into consideration.

Does pass 2 also not take recordings in the Deleted group ito
consideration? Having used your patch for the past two weeks, it seems
like they are skipped entirely, with only expirable non-deleted
recordings taken into consideration.

--
Frontend: P4 3.0GHz, 1.5TB software RAID 5 array
Backend: Quad-core Xeon 1.6GHz, 6.6TB sw RAID 6
Video inputs: Four high-definition over FireWire/OTA
Accessories: 47" 1080p LCD, 5.1 digital, and MX-600
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com