On 27/07/2013 00:24, Zahariev, Boris wrote:
~]$ sudo df -h /nfs/eq-fas3240-001a/vol/a0content1/rcuvb/
FilesystemSize Used Avail Use% Mounted on
eq-fas3240-001a:/vol/a0content1
549G 501M 549G 1% /nfs/eq-fas3240-001a/vol/a0content1
~]$ sudo df -h
Hi Bob
~]# strace -o df.strace.out1 -v -e trace=statfs df -h
/nfs/eq-fas3240-001a/vol/a0content1/rcuvb/
FilesystemSize Used Avail Use% Mounted on
eq-fas3240-001a:/vol/a0content1
656G 501M 655G 1% /nfs/eq-fas3240-001a/vol/a0content1
~]# strace -o
tag 14963 notabug
close 14963
stop
On 07/29/2013 06:24 PM, Zahariev, Boris wrote:
Hi Bob
~]# strace -o df.strace.out1 -v -e trace=statfs df -h
/nfs/eq-fas3240-001a/vol/a0content1/rcuvb/
FilesystemSize Used Avail Use% Mounted on
eq-fas3240-001a:/vol/a0content1
On 07/27/2013 12:26 AM, Zahariev, Boris wrote:
The values for the same file-system differ depending on the file tested?
They shouldn't, no. What does 'strace' tell you about the
relevant system calls? If the system calls are reporting
the incorrect information, the bug lies in the kernel or
Zahariev, Boris wrote:
~]$ sudo df -h /nfs/eq-fas3240-001a/vol/a0content1/rcuvb/
FilesystemSize Used Avail Use% Mounted on
eq-fas3240-001a:/vol/a0content1
549G 501M 549G 1%
/nfs/eq-fas3240-001a/vol/a0content1
~]$ sudo df -h
~]$ sudo df -h /nfs/eq-fas3240-001a/vol/a0content1/rcuvb/
FilesystemSize Used Avail Use% Mounted on
eq-fas3240-001a:/vol/a0content1
549G 501M 549G 1% /nfs/eq-fas3240-001a/vol/a0content1
~]$ sudo df -h /nfs/eq-fas3240-001a/vol/a0content1/rcuniverse/
~]$ sudo df -h /nfs/eq-fas3240-001a/vol/a0content1/rcuvb/
FilesystemSize Used Avail Use% Mounted on
eq-fas3240-001a:/vol/a0content1
549G 501M 549G 1% /nfs/eq-fas3240-001a/vol/a0content1
~]$ sudo df -h /nfs/eq-fas3240-001a/vol/a0content1/rcuniverse/