[mythtv-commits] Ticket #2364: Increase sleep_time in truncate-delete patch to accomodate remote mounts

MythTV mythtv at cvs.mythtv.org
Wed Sep 27 19:17:56 UTC 2006


#2364: Increase sleep_time in truncate-delete patch to accomodate remote mounts
----------------------------+-----------------------------------------------
 Reporter:  ylee at pobox.com  |        Owner:  cpinkham
     Type:  patch           |       Status:  new     
 Priority:  minor           |    Milestone:          
Component:  mythtv          |      Version:  0.20    
 Severity:  medium          |   Resolution:          
----------------------------+-----------------------------------------------
Comment (by ylee at pobox.com):

 I am pleased to report that, with Mike Dean's patch, truncated deletes
 work again on my 0.20 (ATrpms) system, with a couple of minor caveats.

 The three standards I'm using to gauge the patch's behavior are 1)
 mythbackend no longer crashing (even with '-v file'), 2) properly
 truncating the recording (renamed to cifsxxxx or .nfsxxxx), and 3)
 eliminating the remaining stub file after truncation is done. Using NFS on
 my NAS always properly resulted in 1), 2), and 3). Back when I was
 successfully using Boleslaw's truncation patch on 0.19-fixes with the same
 cifs NAS filesystem, [http://www.gossamer-
 threads.com/lists/mythtv/users/208889#208889 only 1) and 2) were true],
 and the same holds for this patch; however, it's easy to [http://www
 .gossamer-threads.com/lists/mythtv/users/209499#209499 work around]
 (although the phrase is now "All file truncates have finished," not "are
 finished.") for the time being. (By the way, [http://www.gossamer-
 threads.com/lists/mythtv/users/220115#220115 I believe] a firmware upgrade
 on the NAS broke both Boleslaw's 0.19-fixes patch and 0.20's pre-patch
 truncation method.)

 As mentioned, the only outstanding issue is 3), having the cifsxxxx stub
 sticking around. My current cifs mount options in /etc/auto.misc are:

 -fstype=cifs,noperm,mapchars,brl,sfu,serverino,directio,iocharset=utf8,rsize=32768,wsize=32768
 ://NAS/RECORDINGS

 Perhaps this will give someone a clue as to fixing 3), but, again, I can
 easily work around this peculiarity for the time being.

 Also note that I have not yet tested a) whether this patch breaks the
 previous 100%-correct truncation behavior seen under NFS and b) whether
 mythtranscode will also truncate properly. (FYI, mythtranscode in 0.20
 apparently attempts to use the truncation method for deleting old versions
 of recordings even when truncation was turned off in mythtv-setup; that
 is, I'd find the old versions renamed to cifsxxxx but otherwise intact.
 Should I open another ticket?)

 In conclusion, my sincerest thanks to Mike and to the other contributors
 in getting this issue resolved.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/2364#comment:7>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list