[mythtv-commits] Ticket #2492: mythtranscode leaving cifsxxxx files behind after transcode finishes
MythTV
mythtv at cvs.mythtv.org
Thu Sep 28 15:19:50 UTC 2006
#2492: mythtranscode leaving cifsxxxx files behind after transcode finishes
----------------------------+-----------------------------------------------
Reporter: ylee at pobox.com | Owner: ijr
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.20
Severity: medium |
----------------------------+-----------------------------------------------
I use a cifs mount for my MythTV recordings. With 0.20 (ATrpms)
mythtranscode will, after completing a transcode, leave behind the
original recording renamed to cifsxxxx (a consequence of using silly
rename, I know) instead of deleting it as it's supposed to (and as it did
in 0.19-fixes).
I don't know how feasible this is from an architectural standpoint, but
could this issue be fixed by having mythtranscode pass along the task of
deleting the original recording to mythbackend's autoexpire? That way the
recording could be deleted using, if set, 0.20's new truncated-delete
feature and, thus, eliminate the last major cause of filesystem lockups
and consequent damaged recordings for those of us stuck with EXT3 for one
reason or another.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/2492>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list