[mythtv-users] Problems Playing Files in Master
Bruce Taber
b.taber at comcast.net
Tue Feb 21 21:14:56 UTC 2012
On 02/21/2012 11:48 AM, Bill Meek wrote:
> Hi;
>
> Not much help, but I'm running on the same commit as you. Playback
> of all recordings works fine over IPv4 or IPv6.
>
> What I don't have is a slave backend, recordings are on the MBE (no
> NFS.)
>
> You didn't mention if 'Master backend override' is set in mythtv-setup
> General. Its an easy change - worth toggling to see if things change.
>
> Storage Groups. I only use the default, so perhaps another difference.
> http://www.mythtv.org/wiki/Storage_Groups#Quick_Rules
>
> I'd start with: -v playback,file and maybe add: --loglevel debug and
> put those on the master, slave and frontend.
>
> If you're building from source, get the last known working commit from
> the "version:" line in mythbackend*.log and then:
>
> git log --patch-with-stat f00f00f..HEAD | less
>
> and you can use less to search thourgh the results.
>
> -- Bill
Thanks Bill. This problem seems to have been attributed to a whole lot
of things piling up. Well, some of the piling on is probably due to my
actions as well. What I noticed was that my storage groups had somehow
gotten full to the gills. I do have the system set for a 1GB Extra disk
space but both disks were maxed out. I went through and manually freed
space by matching the to be expired files and cleaning out the file in
the storage group. That got enough space to work with. Cleanup was
finally done by restoring yesterday's database and using find_orphans.py
to sync things up.
I do have the Master backend override selected on both the master and
slave backends. They are still set.
My storage groups are just default with two disks mounted. They are
formatted xfs but that shouldn't matter.
I'm not sure how it got into the downward spiral but it is working okay
at the moment. I'll be keeping an eye on the storage groups for the time
being.
Thanks,
Bruce
More information about the mythtv-users
mailing list