[mythtv] SVN won't delete symlinks
Dan Wilga
mythtv-dev at dwilga-linux1.amherst.edu
Fri Aug 11 13:14:58 UTC 2006
At 3:37 PM -0400 8/7/06, Chris Pinkham wrote:
>Run the backend with the "-v file" option and look in the logs to see
>if you see any messages relating to deleting the file or symlink.
I believe I found the reason for the problem, and why it only happens
sometimes: Myth is failing to resolve relative symlinks.
In my setup, I have my recordings stored in /media/record, and an
NFS-mounted folder at /media/nfs to move them to when the main HD
becomes to full. I create symlinks like:
something.nuv -> ../nfs/something.nuv
Here's the output of 'mythbackend -v file':
2006-08-11 08:17:22.991 About to unlink/delete file:
'/media/record/3332_20060518165900.nuv'
2006-08-11 08:17:22.999 Error deleting
'../nfs/3332_20060518165900.nuv' could not open
eno: No such file or directory (2)
2006-08-11 08:17:23.006 Delete Error
'/media/record/3332_20060518165900.nuv' ->
'../nfs/3332_20060518165900.nuv'
eno: No such file or directory (2)
2006-08-11 08:17:23.015 Error deleting file:
/media/record/3332_20060518165900.nuv. Keeping metadata in database.
This suggests that Myth is trying to delete the file using ".." in
the path, which is incorrect because mythbackend was not started in
/media/record. To confirm this theory, I stopped mythbackend, cd'd to
/media/record, restarted it, and then deleted the recording. It
worked.
Interestingly, this also explains why previous versions of MythTV
would delete the symlink but not the original file. The difference is
that the older versions would try to delete the real file, fail, and
then delete the symlink and meta data anyway. The way it's done now
is obviously an improvement.
--
Dan Wilga "Ook."
More information about the mythtv-dev
mailing list