mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gregory Giguashvili <Gregoryg@ParadigmGeo.com>
To: "'trond.myklebust@fys.uio.no'" <trond.myklebust@fys.uio.no>
Cc: "Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: RE: O_SYNC option doesn't work (2.4.18-3)
Date: Wed, 7 Aug 2002 20:39:27 +0200	[thread overview]
Message-ID: <EE83E551E08D1D43AD52D50B9F511092E114E1@ntserver2> (raw)

>However if you are thinking that O_SYNC means that you can
>write simultaneously to the same file from 2 different clients, then
>the answer is "the NFS protocol won't allow you to do that".
>The *only* method of ensuring cache consistency in such a case is to
>use POSIX file locking.
I thought that O_SYNC opens the file for synchronous I/O by blocking writes
till the data is written to the disk. In case of NFS mounted disk, this
should work only if "sync" option is present both in export and mount
options, shouldn't it?

In what I see, a simple test doesn't work in the expected way, which is one
client writes to a file opened with O_SYNC on a drive mounted with sync
option and the other client cannot immediatelly see the written data.
Are you saying that this is the way it should be?

Thanks a lot.
Giga



             reply	other threads:[~2002-08-07 17:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07 18:39 Gregory Giguashvili [this message]
2002-08-07 17:43 ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 14:57 Gregory Giguashvili
2002-08-08 15:37 ` Daniel Forrest
2002-08-08 13:48 Jesse Pollard
     [not found] <fa.jepn5rv.uiqrqe@ifi.uio.no>
     [not found] ` <fa.gkqj0av.c661ad@ifi.uio.no>
2002-08-08  7:11   ` Giacomo Catenazzi
2002-08-08  8:06     ` Willy Tarreau
2002-08-08 12:36       ` Alan Cox
2002-08-07 20:48 Jesse Pollard
2002-08-08 10:07 ` Martin Brulisauer
2002-08-07 19:30 Gregory Giguashvili
2002-08-08 13:42 ` Trond Myklebust
2002-08-07 19:24 Gregory Giguashvili
2002-08-07 19:38 ` Trond Myklebust
2002-08-07 21:55 ` Alan Cox
2002-08-07 18:54 Gregory Giguashvili
2002-08-07 18:13 ` Trond Myklebust
2002-08-07 18:15 Jesse Pollard
2002-08-07 17:31 Gregory Giguashvili
2002-08-07 17:19 ` Trond Myklebust
2002-08-07 17:24 Gregory Giguashvili
2002-08-07 16:31 ` Trond Myklebust
2002-08-07 17:17 Gregory Giguashvili
2002-08-07 16:24 ` Trond Myklebust
2002-08-07 20:20   ` Benjamin LaHaise

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EE83E551E08D1D43AD52D50B9F511092E114E1@ntserver2 \
    --to=gregoryg@paradigmgeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®