[mythtv-users] 0.22 autoexpire behavior

Michael T. Dean mtdean at thirdcontact.com
Mon Nov 16 22:23:46 UTC 2009


On 11/16/2009 05:17 PM, Yan Seiner wrote:
> On Mon, November 16, 2009 2:10 pm, Michael T. Dean wrote:
>   
>> On 11/16/2009 05:04 PM, Yan Seiner wrote:
>>     
>>> But it's still not autoexpiring anything that actually takes up space.
>>>
>>> selene:/data20/mythtv/recordings# df
>>> Souborový systém      1K bloků   Použité     Volné Uži% Pipojeno
>>> do
>>> /dev/md20            1922866224 1901450808   1880220 100% /data20
>>>
>>> With 1.8 GB free, and expire running every 15 minutes, it should be
>>> dumping 58 GB of recordings....
>>>       
>> It's still 100% full, therefore, Myth can not start a new recording.
>> Therefore Myth will never start expiring.  Get that usage down to
>> something less than 100% (ideally with a few percent free to handle the
>> time between when Myth starts recording and when the autoexpire thread
>> runs) and then start recording something (anything) to get the
>> autoexpire to actually do stuff.
>>     
>
> So does myth look at the % free number?

Not so much, but it tries to write a multi-gigabyte file to the file 
system--and if the file system fills up, bad things happen.  If it fills 
up before the autoexpirer is caled to start deleting things, nothing 
will be deleted.

Remember, most file systems have some reserved blocks percentage that 
only root can use.

Just truncate some of the recordings that Myth will be expiring when it 
expires the 58GiB of recordings you want it to expire.  If you get a 
good 20GiB freed up (which would be about 1% of your file system), it 
should have plenty of room to handle autoexpiring while recording at 
least one show.

Mike


More information about the mythtv-users mailing list