All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom McNeal <trmcneal@attbi.com>
To: Rex Dieter <rdieter@math.unl.edu>,
	NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories on NFS mounts
Date: Thu, 11 Jul 2002 13:05:18 -0700	[thread overview]
Message-ID: <3D2DE4FE.35B1ABA7@attbi.com> (raw)
In-Reply-To: 200207111414.03258.rdieter@math.unl.edu

Rex Dieter wrote:
> 
> Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> 
> > >>>>> " " == Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
> >      > What if the NFS stuff is not mounted with sync or explicitly
> >      > mounted async? Will an nfsd still do synchronous writes to
> >      > directories?
> 
> > Of course. It is not possible for the NFS client to switch this
> > behaviour off, since it is part of the server side specifications in
> > the protocol.
> > The only thing that can screw you up is if you use the 'async' option
> > in /etc/exports on the server.
> 
> How is specifying 'async' in /etc/exports on the NFS server different than a
> NFS client explicitly mounting async?
> 
> -- Rex


The /etc/exports async option allows the server to tell the client
that it has indeed written data/metadata to the disk, regardless
of what has actually happened.

So, the client sync/async affects *when* the client writes to the
server, and the server sync/async affects *how* (OK, and *when*) the 
server replies to the client.  

Regards -

Tom

--
------------------------------------------------------------
Tom McNeal       trmcneal@attbi.com     (650)906-0761 (cell) 
------------------------------------------------------------


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
PC Mods, Computing goodies, cases & more
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-07-11 20:01 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E17SjDh-00067R-00@usw-sf-list2.sourceforge.net>
2002-07-11 19:08 ` redhat 2.4.18-5 client huge slowdown Rex Dieter
2002-07-11 19:14 ` [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories on NFS mounts Rex Dieter
2002-07-11 20:05   ` Tom McNeal [this message]
2002-07-11 19:29 ` redhat 2.4.18-5 client huge slowdown Rex Dieter
2002-07-12 12:07   ` Trond Myklebust
2002-07-09 13:49 [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories on NFS mounts Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2002-07-09 13:49 Trond Myklebust
2002-07-09 14:06 ` Richard B. Johnson
2002-07-09 14:06 ` Richard B. Johnson
2002-07-09 14:08   ` Trond Myklebust
2002-07-09 15:06     ` Richard B. Johnson
2002-07-09 15:06     ` Richard B. Johnson
2002-07-09 16:56       ` Alan Cox
2002-07-09 16:56         ` Alan Cox
2002-07-09 17:22         ` Richard B. Johnson
2002-07-09 17:22           ` Richard B. Johnson
2002-07-09 19:11           ` Alan Cox
2002-07-09 19:11             ` Alan Cox
2002-07-09 19:13             ` Richard B. Johnson
2002-07-09 19:59               ` Alan Cox
2002-07-09 19:59                 ` Alan Cox
2002-07-09 19:50                 ` Richard B. Johnson
2002-07-09 19:50                 ` Richard B. Johnson
2002-07-15  7:52                   ` Sean Hunter
2002-07-15 12:45                     ` Richard B. Johnson
2002-07-15 12:45                     ` Richard B. Johnson
2002-07-15 13:35                       ` Matthias Andree
     [not found]                         ` <mit.lcs.mail.linux-kernel/20020715133507.GF32155@merlin.emma.line.org>
2002-07-15 14:49                           ` Patrick J. LoPresti
2002-07-15 15:18                             ` Matthias Andree
     [not found]                               ` <mit.lcs.mail.linux-kernel/20020715151833.GA22828@merlin.emma.line.org>
2002-07-15 16:10                                 ` Patrick J. LoPresti
2002-07-15 18:16                                   ` Matthias Andree
     [not found]                                     ` <mit.lcs.mail.linux-kernel/20020715181650.GA20665@merlin.emma.line.org>
2002-07-15 18:56                                       ` Patrick J. LoPresti
2002-07-15 20:50                                         ` Matthias Andree
2002-07-15 16:16                             ` Alan Cox
2002-07-15 15:19                               ` Matthias Andree
2002-07-15 16:45                                 ` Alan Cox
2002-07-15 15:38                               ` Patrick J. LoPresti
2002-07-15 16:55                                 ` Alan Cox
2002-07-15 20:17                                   ` Patrick J. LoPresti
2002-07-16  1:40                                     ` jw schultz
2002-07-15 15:20                         ` Bill Rugolsky Jr.
2002-07-15 15:35                           ` Matthias Andree
2002-07-15 16:14                             ` Bill Rugolsky Jr.
2002-07-09 19:13             ` Richard B. Johnson
2002-07-09 14:08   ` Trond Myklebust
2002-07-10  6:33   ` Alex Riesen
2002-07-10 11:20     ` Richard B. Johnson
2002-07-11 10:52 ` Matthias Andree
2002-07-11 11:26   ` Trond Myklebust

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=3D2DE4FE.35B1ABA7@attbi.com \
    --to=trmcneal@attbi.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=rdieter@math.unl.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.