On May 3, 2012, at 3:04 PM, Glenn Cooper wrote:
I never really paid attention to this but a file on an NFS mount is showing 64M in size, but when copying the file to a local drive, it shows 2.5MB in size.
My NFS server is hardware Raided with a volume stripe size of 128K were the volume size is 20TB, my local disk is about 500GB.
Is this due to my stripe size?
Nuggets are appreciated.
By the way, this is only across NFS as when ssh'd into the server, the file size shows 2.5M, same as the clients when its local so its seems NFS is the culprit.
I have r/wsize tweaked but thats it.
Wild guess - cached file attributes not getting updated properly in the NFS client? Has the actual file size changed recently, like in the last few hours or days?
Cheers, Glenn
Something more relevant perhaps, mount options via FSTAB on the server are;
/dev/### /mountpoint xfs defaults,allocsize=64m,relatime,logbufs=8,logbsize=256k 0 0
Notice the allocsize of 64MB, perhaps relatime might be playing a role as well?
I will remove allocsize first and report back.
- aurf
On 05/03/2012 09:16 PM, aurfalien wrote:
On May 3, 2012, at 3:04 PM, Glenn Cooper wrote:
I never really paid attention to this but a file on an NFS mount is showing 64M in size, but when copying the file to a local drive, it shows 2.5MB in size.
My NFS server is hardware Raided with a volume stripe size of 128K were the volume size is 20TB, my local disk is about 500GB.
Is this due to my stripe size?
Nuggets are appreciated.
By the way, this is only across NFS as when ssh'd into the server, the file size shows 2.5M, same as the clients when its local so its seems NFS is the culprit.
I have r/wsize tweaked but thats it.
Wild guess - cached file attributes not getting updated properly in the NFS client? Has the actual file size changed recently, like in the last few hours or days?
Cheers, Glenn
Something more relevant perhaps, mount options via FSTAB on the server are;
/dev/### /mountpoint xfs defaults,allocsize=64m,relatime,logbufs=8,logbsize=256k 0 0
Notice the allocsize of 64MB, perhaps relatime might be playing a role as well?
I will remove allocsize first and report back.
- aurf
Is it possible that you have 2 files with (almost) the same name? Check the inode of the file? And maybe copy it to subfolder?
Ljubomir Ljubojevic wrote:
On 05/03/2012 09:16 PM, aurfalien wrote:
On May 3, 2012, at 3:04 PM, Glenn Cooper wrote:
I never really paid attention to this but a file on an NFS mount is showing 64M in size, but when copying the file to a local drive, it shows 2.5MB in size.
<snip>
By the way, this is only across NFS as when ssh'd into the server, the file size shows 2.5M, same as the clients when its local so its seems NFS is the culprit.
<snip>
Wild guess - cached file attributes not getting updated properly in the NFS client? Has the actual file size changed recently, like in the last few hours or days?
Something more relevant perhaps, mount options via FSTAB on the server are;
/dev/### /mountpoint xfs defaults,allocsize=64m,relatime,logbufs=8,logbsize=256k 0 0
Notice the allocsize of 64MB, perhaps relatime might be playing a role as well?
I will remove allocsize first and report back.
Is it possible that you have 2 files with (almost) the same name? Check the inode of the file? And maybe copy it to subfolder?
Two questions: are you looking at the file *without* the directory being NFS mounted? Could you have accidentally created it under the mountpoint? Second - could it be a sparse file?
mark
On May 3, 2012, at 4:01 PM, m.roth@5-cent.us wrote:
Ljubomir Ljubojevic wrote:
On 05/03/2012 09:16 PM, aurfalien wrote:
On May 3, 2012, at 3:04 PM, Glenn Cooper wrote:
> I never really paid attention to this but a file on an NFS mount is > showing 64M in size, but when copying the file to a local drive, it > shows 2.5MB in size.
<snip> >>>> By the way, this is only across NFS as when ssh'd into the server, the >>>> file size shows 2.5M, same as the clients when its local so its seems >>>> NFS is the culprit. <snip> >>> Wild guess - cached file attributes not getting updated properly in the >>> NFS client? Has the actual file size changed recently, like in the >>> last few hours or days? >> >> Something more relevant perhaps, mount options via FSTAB on the server >> are; >> >> /dev/### /mountpoint xfs >> defaults,allocsize=64m,relatime,logbufs=8,logbsize=256k 0 0 >> >> Notice the allocsize of 64MB, perhaps relatime might be playing a role >> as well? >> >> I will remove allocsize first and report back. > > Is it possible that you have 2 files with (almost) the same name? Check > the inode of the file? And maybe copy it to subfolder?
Two questions: are you looking at the file *without* the directory being NFS mounted? Could you have accidentally created it under the mountpoint?
Hi all,
It was my fstab mount option of allocsize=64m that caused this issue.
Just wanted to report back.
Thanks to all who responded to my call for help, I very much appreciate it.
- aurf
-
aurfalien -
Ljubomir Ljubojevic -
m.roth＠5-cent.us