[mythtv] Fwd: [mythtv-users] Myth autoexpiring brand new shows

Michael T. Dean mtdean at thirdcontact.com
Mon Oct 13 17:09:37 UTC 2008

On 10/12/2008 06:52 PM, michael bishop wrote:
> I've found that my mythbackend was preferring a local storage
> directory(that was full) over networked ones(with tons of space).
> that led to it expiring shows it just recorded when it had plenty of
> space.
> I'm working on a patch which will kick the weight of a storage group +30
> when the drive is 'full' so that it will prefer drives with more room

Did you read the whole thread(s)?

-users portion:
-dev portion:
And, IMHO, the first post in this sub-thread is relevant:

Ticket #5746
discussion of #5746

Just remember that not everyone feels that preferring network storage is 
better (even if it has free space that local drives don't).  IMHO (as I 
mentioned, before - 
http://www.gossamer-threads.com/lists/mythtv/users/347073#347073 ), the 
/right/ solution is for the user to ensure that recording files are 
moved to network storage when they're certain the network is available, 
rather than having Myth record directly to network storage.  In other 
words, always keep the remote storage full and leave space on local storage.

There even happens to be a user-job script, myth_archive_job.pl, that 
was designed for exactly this type of thing (though it's pre-storage 
groups, it works well even in a storage groups setup).  It can be run as 
a user job (so it's automatically run after a recording) to ensure that 
space is available on your local drives and that the remote drives are 
full.  It would even be easy to modify it to be storage groups aware, so 
the directories wouldn't have to be specified in the script.

Mike--who will /always/ have Myth prefer local storage, regardless of 
whether your patch goes in or not

More information about the mythtv-dev mailing list