[lkml]   [2002]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: O_SYNC option doesn't work (2.4.18-3)
>>>>> " " == Gregory Giguashvili <> writes:

> Well, this is the way it's been working on all UN*X platforms I
> know. In fact, we came across this problem with NFS clients
> being unable to synchronize on Linux.

Sorry. AFAICS O_SYNC only affects writes (just like we do).

As for reads: all commercial NFS clients I know of will check data
cache consistency on open(). They will assume that they can cache
attributes and data as per the documentation in 'man 5 nfs' (although
you can turn this off by using the 'noac' mount option).

Furthermore, even with 'noac' they *all* have problems with races in
the sort of scenario you describe because there is no atomic
GETATTR+READ operation.

Bottom line: If you want the sort of data cache consistency you are
describing, you *have* to use file locking.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:27    [W:0.034 / U:0.116 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site