mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Forrest <forrest@lmcg.wisc.edu>
To: Gregory Giguashvili <Gregoryg@ParadigmGeo.com>
Cc: "Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>,
	"'trond.myklebust@fys.uio.no'" <trond.myklebust@fys.uio.no>,
	"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
	"'pollard@tomcat.admin.navo.hpc.mil'" 
	<pollard@tomcat.admin.navo.hpc.mil>,
	"'bcrl@redhat.com'" <bcrl@redhat.com>,
	"'cks@utcc.utoronto.ca'" <cks@utcc.utoronto.ca>
Subject: Re: O_SYNC option doesn't work (2.4.18-3)
Date: Thu, 8 Aug 2002 10:37:27 -0500 (CDT)	[thread overview]
Message-ID: <200208081537.KAA09749@radium.lmcg.wisc.edu> (raw)
In-Reply-To: <EE83E551E08D1D43AD52D50B9F511092E114E5@ntserver2> (message from Gregory Giguashvili on Thu, 8 Aug 2002 16:57:59 +0200)

Gregory Giguashvili <Gregoryg@ParadigmGeo.com> writes:

>> The above sequence works OK, but it's still problematic since it
>> doesn't ensure that the data is coming from the server instead of
>> NFS cache. In one of my previous discussions on this list, I was
>> told to use the following technique to flush NFS buffers. It turns
>> out that acquiring write lock using fcntl (F_SETLK) interface acts
>> as NFS write barrier and flushes all the file NFS buffers. So, the
>> above sequence would result in the following one:
>> 
>> - lock_file (doesn't have to be a lockd lock)
>> - open_file (O_SYNC)
>> - if (read) fcntl (F_SETLK) (doing lock/unlock here to flush NFS buffers)
>> - read/write file
>> - if (write) fcntl (F_SETLK) (doing lock/unlock here to flush NFS buffers)
>> - close_file
>> - unlock_file

I have been working in a mixed Linux/Solaris environment and this is
what works for me.  (>40 machines reading/writing/modifying the same
files at the same time for hundreds of iterations with no errors.)

- open()

  To get a file descriptor that can be locked

- fcntl(F_SETLK)

  To ensure that all other clients have written their data to the file
  and to clear the client cache

- fchmod()

  File attributes (most importantly file size) were cached when the
  file was opened, these may change between that time and when the
  lock is granted, a side effect of fchmod() is to refresh the file
  attributes from the server

- lseek() / read() / write()

  If appending, it is important to lseek(SEEK_END) at this point to
  make sure you are at the true end of file

- close()

  This will flush any data written and remove the lock


If anyone experiments with this with systems other than Linux/Solaris
I would be interested in knowing if it works there also.

-- 
+----------------------------------+----------------------------------+
| Daniel K. Forrest                | Laboratory for Molecular and     |
| forrest@lmcg.wisc.edu            | Computational Genomics           |
| (608)262-9479                    | University of Wisconsin, Madison |
+----------------------------------+----------------------------------+

  reply	other threads:[~2002-08-08 15:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 14:57 Gregory Giguashvili
2002-08-08 15:37 ` Daniel Forrest [this message]
  -- strict thread matches above, loose matches on Subject: below --
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: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=200208081537.KAA09749@radium.lmcg.wisc.edu \
    --to=forrest@lmcg.wisc.edu \
    --cc=Gregoryg@ParadigmGeo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=cks@utcc.utoronto.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pollard@tomcat.admin.navo.hpc.mil \
    --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®