Linux NFS development
 help / color / mirror / Atom feed
From: George Garvey <tmwg-nfs@inxservices.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS Performance with sync or async
Date: Tue, 31 May 2005 09:54:19 -0700	[thread overview]
Message-ID: <20050531165419.GC20637@inxservices.com> (raw)
In-Reply-To: <1117313519.10746.20.camel@lade.trondhjem.org>

On Sat, May 28, 2005 at 01:51:59PM -0700, Trond Myklebust wrote:
> Note that there are two "sync" options: one affects the server behaviour
> causing it to always make sure that the data reaches the disk if/when
> the client requests it (see 'man 5 exports') and the other affects the
> client (and is a mount option).

   Thanks. I'm an idiot. I need to recheck everything based on this
misunderstanding. I may have made some other mistakes.
   I believed I saw some people talking about changing the mount
default to sync from async. That may be bad memory, but helped my
misconception ;)


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-05-31 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-28  2:45 NFS Performance with sync or async Lever, Charles
2005-05-28 12:53 ` George Garvey
2005-05-28 20:51   ` Trond Myklebust
2005-05-31 16:54     ` George Garvey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-28 16:13 Lever, Charles
2005-05-31 16:58 ` George Garvey
2005-05-27 22:16 George Garvey

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=20050531165419.GC20637@inxservices.com \
    --to=tmwg-nfs@inxservices.com \
    --cc=nfs@lists.sourceforge.net \
    /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