[mythtv] Detection of shared disks in storage groups
Chris Pinkham
cpinkham at bc2va.org
Sun Dec 3 06:41:57 UTC 2006
* On Sat Dec 02, 2006 at 11:43:28AM -0800, Gregorio Gervasio, Jr. wrote:
> In mythbackend/backendutil.cpp, BackendQueryDiskSpace has a 16KB fudge
> factor for the total space when detecting shared disks:
I put that in because my NFS clients mounting using 8KB read/write sizes
see the following:
taz:/taz/video1 288435168 161252104 127183064 56% /taz/video1
taz:/taz/video2 115380192 52464544 62915648 46% /taz/video2
taz:/taz/video3 76920416 59044056 17876360 77% /taz/video3
While on the fileserver, I get this:
/dev/hdc1 288435168 161252120 127183048 56% /taz/video1
/dev/hdb1 115380192 52464548 62915644 46% /taz/video2
/dev/hdd1 76920416 59044056 17876360 77% /taz/video3
So I'm seing a difference of 16KB on video1, 4KB on video2 and video3
matches exactly.
> Dir: slave1.home:/home/mythtv/store.v
> Location: Local
> Drive ID: 1
> TotalKB : 397553664
> UsedKB : 176041984
> FreeKB : 221511680
>
> Dir: slave2.home:/home/mythtv/store.v
> Location: Remote
> Drive ID: 2
> TotalKB : 397541376
> UsedKB : 176029696
> FreeKB : 221511680
>
> ie, the size discrepancy is 12288KB. Don't know if it matters but the
That's pretty big.
> I'm not sure what problems this will cause but just in case,
> I've bumped up the fudge factor in my local tree.
I don't think it will matter much, but in your case, the usedKB is
off by that same amount, did you adjust the fudge on that also?
What did you bump it up to?
--
Chris
More information about the mythtv-dev
mailing list