From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Gregory Giguashvili <Gregoryg@ParadigmGeo.com>
Cc: "'Jesse Pollard'" <pollard@tomcat.admin.navo.hpc.mil>,
"Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: O_SYNC option doesn't work (2.4.18-3)
Date: 08 Aug 2002 15:42:30 +0200 [thread overview]
Message-ID: <shsbs8d31rt.fsf@charged.uio.no> (raw)
In-Reply-To: <EE83E551E08D1D43AD52D50B9F511092E114E4@ntserver2>
>>>>> " " == Gregory Giguashvili <Gregoryg@ParadigmGeo.com> writes:
> When the writer closes the file, how do you make the readers
> see the latest changes (assuming that you always open/close
> files per transaction type).
There is a convention amongst NFS clients that each client will always
flush *all* changes to the server upon close(), and it will always
check the file attributes upon a call to open() (and if the mtime or
file size have changed, one flushes the page cache).
This suffices to guarantee file cache consistency *provided* that only
one client opens the file at any given time.
If locking is used, all changes are flushed to the server upon
taking/releasing a lock, and the page cache is guaranteed to get
flushed upon taking a lock.
Cheers,
Trond
next prev parent reply other threads:[~2002-08-08 13:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 19:30 O_SYNC option doesn't work (2.4.18-3) Gregory Giguashvili
2002-08-08 13:42 ` Trond Myklebust [this message]
-- 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: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:39 Gregory Giguashvili
2002-08-07 17:43 ` 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=shsbs8d31rt.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Gregoryg@ParadigmGeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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