[mythtv] Expiry problem

[Ian Dall]

On Wed, 2012-04-18 at 18:44 +1000, Michael Watson wrote:
> On 18/04/2012 6:34 PM, Ian Dall wrote:
> > On Wed, 2012-04-18 at 10:37 +1000, Michael Watson wrote:
> >> On 18/04/2012 9:10 AM, Ian Dall wrote:
> >>> Hi,
> >>>
> >>> 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.
> >>>
> >>>
> >>> * I've upgraded again but it is too early to tell if the problem is
> >>> still there.
> >>>
> >> More a question for the mythtv-users list.
> >> But sounds like a permission problem.
> > Thanks, but I don't think so. Firstly I have checked, secondly this
> > started happening after an upgrade with no change in configuration and
> > thirdly I know of no unix or nfs permissions which allow create but not
> > delete privilege and clearly files are being created or my disk wouldn't
> > fill up ;-(
> That depends on your NFS configuration, and which machine writes the 
> file, and which machine is trying to delete the file.
> The permissions of a file that has not been deleted, are they the say 
> when viewed from each machine?

Good point, but no. On each machine I did
        su mythtv
        touch /var/media/myth/mythtv/foo
        rm /var/media/myth/mythtv/foo
        ps -fp $(cat /var/run/mythbackend.pid)

and everything checks out.

As I said, I've upgraded mythtv to v0.26-pre-25-something and turned on
"file" logging. I've also rebooted the virtual machine which was running
mythmaster. It had been up for 59 days and was low on free memory and
swap (I don't recall why). So I'll now wait and see if it happens again.

Thanks for your thoughts.

        
-- 
Ian Dall <ian at beware.dropbear.id.au>