inconsistent file content after killing nfs daemon

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Fri, Jan 11, 2002 at 10:37:37AM +0100, eric chacron wrote:
 
> To answer your question, the problem seems to be reproductible only in
> asynchronous mode (without O_SYNC).
> I have reproduced the case ( without O_SYNC) using different record sizes:
> from 1 K to 64 K, but not with 512 bytes.
> It makes sense that the the zeroed holes in the file are caused by the nfs
> client absence of serialisation/ ordering as the file is used in extension.
> With O_SYNC i haven't reproduced the same problem for the moment.

Right --- that's standard unix semantics for writeback.  Writes to
backing store are completely unordered unless you request ordering
with O_SYNC or f[data]sync.

Cheers,
 Stephen





[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux