[mythtv-users] MythTV accessing 'Videos' storage group hourly?

[thigger]

On Sun, Mar 6, 2016 at 5:10 PM, Paul Harrison <mythtv at sky.com> wrote:
> On 06/03/16 16:52, Jonatan Lindblad wrote:
>> Den 2016-03-06 kl. 17:09, skrev Paul Harrison:
>>> What version of MythTV are you using?
>>> Are you using a custom config directory or just using the default of
>>> ~/.mythtv ? Is it located on a different drive than the video storage
>>> groups?
>> That is certainly one possible cause.  However, the OP's logs indicate
>> that the theme is Mythbuntu and that the version is 0.27.4.  This theme is
>> not included in themes.zip from
>> http://themes.mythtv.org/themes/repository/0.27.4/themes.zip. When the
>> frontend is looking for this theme's themeinfo.xml file it fails to find it
>> in the Temp storage group and falls back to search all storage groups.
> So the question is why do we fall back to searching all storage groups? I
> can see how we may need to continue the search for recordings that can't be
> found in the default storage group but not for most other files. In this
> case we only care about what is in Temp?

It's fixes/0.27 from git - I haven't compiled for a while but I've
just checked and it claims to be up to date.
The install is now just over 10 years old on the (mostly) the same
hardware; all directories are whatever the defaults were back then
(only ever installed from source) - it certainly appears to be using
~/.mythtv. The home partition is located on an SSD (along with / );
the video storage group has two directories included -
/store/mythtv/videos (on a local hard drive) and
/mnt/net/smb/hippocampus/Media/Videos (remote windows machine, using
autofs to wake it on access)

I've not used storage groups before but it seems to work much better
for including multiple directories (having switched to just including
both directories in the frontend I've already had a wifely complaint
that she has to go through the entire directory tree from /mnt/ to get
to the videos she wants). Previously we just had the local storage.

It certainly seems an odd decision to scan all storage groups for a
file; I would have thought the benefit of scanning unrelated groups
would be minimal. I'm not particularly familiar with the code since
about 0.19 though so presumably there are reasons for this?

Thanks for looking into it. I'm going to try switching back to storage
groups with the theme updater switched off.

tom