[mythtv-users] storage directories

[Mark Small]

On July 11, 2010 20:59:22 Michael T. Dean wrote:
>   On 07/11/2010 06:56 PM, Mark Small wrote:
> > On July 10, 2010 17:34:08 Raymond Wagner wrote:
> >> On 7/10/2010 15:15, Mark J. Small wrote:
> >>> So here's my question:  How do I stop recording to the third directory
> >>> (the one on the slave)?
> >>
> >> Remove that directory from any storage groups that it shows up on in
> >> mythtv-setup on the slave backend, and then restart the backend.
> >
> > Sounds great, except that the directory isn't in any storage groups on
> > the slave.  In fact there are no storage groups defined on the slave. 
> > Maybe I should create one?
>
> It's inherited from the master backend.  Remote backend storage group
> /directory lists/ simply override the lists defined on the master
> backend.  Or, put another way, you can /define/ storage groups (SG names
> and their associated list of directories) only on the master backend;
> you simply (and only) override storage group directory lists on the
> remote backends.  This is exactly why the /proper/ solution for the
> majority of users is to do as you've done--define storage groups /only/
> on the master backend.  Then, when you want to add or remove a directory
> from a storage group, you only need to make that change in a single
> location--the master backend's mythtv-setup.
>
> IMHO, the /only/ reason anyone should ever specify a list of directories
> on anything other than the master backend is if the user has
> misconfigured his/her system and for some reason wants to use a specific
> directory name only on one system or another but--and here's the
> "misconfiguration" part--for some crazy reason has created said
> directory on the system that shouldn't use that directory.
>
> The master backend should have a list of *all* directories used by *all*
> hosts.  You may add a directory path for a directory that exists on all,
> some, or only one of the hosts (even if it doesn't exist on the master
> backend).
>
> http://www.gossamer-threads.com/lists/mythtv/users/423104#423104 has a
> much more extensive description.
>
> Mike

Thanks, Mike.

Since the mysterious storage directory is not listed in mythtv-setup on either 
the master or the slave, is there any way that I can find out where it came 
from and how to get rid of it?  Is it some old cruft sitting in the database 
from way back when (I don't remember what version I started with, maybe 0.14 
or so).

The slave backend was my original master (and only) backend.  The mysterious 
directory only showed up with version 0.22 or 0.23, also around the time that 
I switched master backend duties with my new file server (an ARM based QNAP 
NAS device).  I may have originally and briefly used the mysterious storage 
directory when I was first testing mythtv, before I added a massive (for its 
day) 160 GB hard drive to hold recordings.

Is it time to go digging in the database?

Mark