[mythtv-commits] Ticket #6503: GetFilesystemInfos, TotalKB: -1 should be ignored

MythTV mythtv at cvs.mythtv.org
Sun Apr 26 08:52:57 UTC 2009

#6503: GetFilesystemInfos, TotalKB: -1 should be ignored
 Reporter:  nick at kreucher.net  |        Owner:  cpinkham  
     Type:  defect             |       Status:  assigned  
 Priority:  minor              |    Milestone:  0.21.1    
Component:  MythTV - General   |      Version:  0.21-fixes
 Severity:  medium             |   Resolution:            
  Mlocked:  0                  |  

Comment(by nick at kreucher.net):

 Right, seems obvious now... starting either backend before the fs is
 mounted results in -1, but if it's mounted (ex, by me requesting an ls of
 the dir to trigger autofs), correct sizing is reported. This even on both
 backends (see below). However, problem of myth not knowing which is local
 remains (is this important?). Local should be pacifico, but instead both
 backends think it's remote:

 pacifico log:
 2009-04-26 01:37:17.300 AutoExpire: ExpireRecordings()
 2009-04-26 01:37:17.307 Maximal bitrate of busy encoders is 0 KB/min
 --- GetFilesystemInfos directory list start ---
 Dir: pacifico:/var/lib/mythtv/recordings
      Location: Remote
      Drive ID: 1
      TotalKB : 878560256
      UsedKB  : 236894208
      FreeKB  : 641666048

 Dir: guinness:/var/lib/mythtv/recordings
      Location: Remote
      Drive ID: 1
      TotalKB : 878560256
      UsedKB  : 236894208
      FreeKB  : 641666048

 --- GetFilesystemInfos directory list end ---

 guinness log:
 2009-04-26 01:37:06.226 Enabled verbose msgs:  important general file
 2009-04-26 01:37:06.237 SG(): CheckAllStorageGroupDirs(): Checking All
 Storage Group directories
 2009-04-26 01:37:07.239 Connecting to master server:
 2009-04-26 01:37:07.241 Connected successfully

 So it seems the CAUSE of the -1 is because of statfs+autofs+ghost option,
 and CAUSE of both "Remote" is using autofs+nfsv4 (no bind mount for local
 fs). Ok, I can switch to nfsv3 and nix ghosting as a next step.

 However, original bug report of Myth not correctly handling -1 within
 GetFilesystemInfos remains. I see some dups... has error handling been
 added to trunk?

 Also, should GetFilesystemInfos get some attention around filesystem
 detection, or are the side effects of autofs+ghost and/or autofs+nfs4
 assumed a sysadmin problem?

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

More information about the mythtv-commits mailing list