ian at beware
Apr 22, 2012, 8:26 AM
On Mon, 2012-04-23 at 00:44 +0930, Ian Dall wrote:
> On Wed, 2012-04-18 at 21:32 -0400, Michael T. Dean wrote:
> > On 04/17/2012 07:10 PM, Ian Dall wrote:
> > > I have been running a recent 0.25 pre-release(*) and have run into
> > > problems with expiry. What happens is that the disk fills up, the expiry
> > > thread runs, deletes the entry from the database, but does not delete
> > > the actual files containing the recording. Since the disk is still full,
> > > it goes ahead and deletes the next show and in a short space of time
> > > there is a full disk, and all programs which allow auto expire have been
> > > deleted from the DB. I recover the DB from backup and manually delete
> > > files which have been recorded since the backup, but obviously it is
> > > annoying to have to do this.
> > >
> > > Possibly relevant is that a) I have a separate master and slave backend
> > > and b) am using NFS for the storage. The logs don't show anything
> > > interesting. Mythtv *thinks* it is doing the right thing. There are
> > > messages about expiring recordings, but nothing to do with failing to
> > > delete a file.
> > >
> > > I'd appreciate any clues about what could cause this or how to debug it.
> > >
> > Are the expired shows in the Deleted recording group? Watch Recordings,
> > MENU|Change Group Filter, then select "Deleted" and see if any that the
> > backend logs say were expired are there.
> Ah! It took a while, but I think I have caught the misbehaviour in the
> act. I had a recording from an iptv "tuner". This should have been about
> 1 hour long, but the file was still open (as reported by lsof) and
> growing 2 hours later, even though the show showed as finished in "Watch
> Recordings". The entire file was watchable.
And I should add, in the system status information the ipv "tuner" was
shown as NOT recording...
Ian Dall <ian [at] beware>
mythtv-dev mailing list
mythtv-dev [at] mythtv