Re: [NFS] blocks of zeros (NULLs) in NFS files in kernels >= 2.6.20

[Aaron Straus <aaron@merfinllc.com>]

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

Hi,

On Sep 11 01:48 PM, Chuck Lever wrote:
> Were you able to modify your writer to do real fsync system calls?  If  
> so, did it help?  That would be a useful data point.

Yes/Yes.  Please see the attached tarball sync-test.tar.bz2.

Inside you'll find the modified writer:  writer_sync.py

That will call fsync on the file descriptor after each write.

Also I added the strace and wireshark data for the sync and nosync
cases.

Note these are all tested with latest linus git:  

  d1c6d2e547148c5aa0c0a4ff6aac82f7c6da1d8b

> Practically speaking this is often not enough for typical  
> applications, so NFS client implementations go to further (non- 
> standard) efforts to behave like a local file system.  This is simply  
> a question of whether we can address this while not creating  
> performance or correctness issues for other common use cases.

Yep, I agree.  I'm not saying what we do now is "wrong" per the RFC
(writing the file out of order).  It's just different from what we've
done in the past (and somewhat unexpected).

I'm still hoping there is a simple fix... but maybe not... :(

Thanks!

					=a=

-- 
===================
Aaron Straus
aaron@merfinllc.com

[-- Attachment #2: sync-test.tar.bz2 --]
[-- Type: application/octet-stream, Size: 15200 bytes --]