[mythtv] Ticket #6846: FreeSpace calculations don't work correctly

Eric Bosch eric.bosch at comcast.net
Sat Aug 15 15:30:29 UTC 2009


MythTV wrote:
> #6846: FreeSpace calculations don't work correctly
> ------------------------------------+---------------------------------------
>  Reporter:  eric.bosch at comcast.net  |        Owner:  ijr 
>      Type:  defect                  |       Status:  new 
>  Priority:  minor                   |    Milestone:  0.22
> Component:  MythTV - General        |      Version:  head
>  Severity:  medium                  |   Resolution:      
>   Mlocked:  0                       |  
> ------------------------------------+---------------------------------------
> 
> Comment(by sphery <mtdean at thirdcontact.com>):
> 
>  Is this fixed by #6582 ?
> 
Ok, I just tried patch 6582 and that is still not returning the correct
results.  I think the correct way to fix this issue is to first
determine if the special directories actually reside on the same
physical filesystem (looking at results of df (mounted on column) or
Filesystem column.  For NFS mounts, this might be a little more complex,
as the remote backend would have to determine the same results and
return them.  One issue I have with it is that the correction that is
built in for nfs mounts is not working properly either, in that the
reported size difference is greater than the correction.  I have 2
filesystems, one local, one NFS mounted.  The master backend has a
/video directory which is a partition of it's own, and contains
directories for LiveTV and Videos, with a total drive capacity of 888
MB, and the slave backend machine has a /video directory that is
actually on / (root) and a total capacity of 930MB, with the same
scenario, LiveTV and Video directory, and in both cases these
directories are NFS mounted to the other machine.  With or without the
patch, it is reporting 3.5TB of total storage, where it is actually much
less than that.


More information about the mythtv-dev mailing list