From: "Paul Cunningham" <paulcunningham@sprintmail.com>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: async vs. sync
Date: Mon, 22 Nov 2004 17:07:56 -0500 [thread overview]
Message-ID: <030901c4d0df$b9664bf0$2801a8c0@PAULLAPTOP1> (raw)
In-Reply-To: 1101158068.11196.71.camel@lade.trondhjem.org
Sorry, I must have missed the export option in a previous message. As I
shake the cobwebs, I cannot remember an async export option used to increase
performance with a warning from the man page "allows the NFS server to
violate the NFS protocol".
Sounds like a dangerous option. Perhaps I'm too far removed from this now,
but the applicable mount options were async and v3. The server then should
adhere to the mount request from the client regardless of an export option.
This all assumes v3 is available on the server. Scanning the man page on my
various Linux boxes I cannot find a v3 mount option, the issue is becoming
much clearer now!
So how does a client mount NFS v3 with Linux?
Paul Cunningham
----- Original Message -----
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "Paul Cunningham" <paulcunningham@sprintmail.com>
Cc: <nfs@lists.sourceforge.net>
Sent: Monday, November 22, 2004 4:14 PM
Subject: Re: [NFS] async vs. sync
må den 22.11.2004 Klokka 16:04 (-0500) skreiv Paul Cunningham:
> It has been a few years, but I remember some of the async details. I
> always
> used async for performance reasons, and much testing was performed to
> assure
> no data would be lost. If a client sent an async write to the server,
> the
> call could return prior to data being flushed to disk. The data would
> make
> it to disk once the server decided to write it or the client sends in
> a
> COMMIT. At some point in time the client will attempt to close the
> file,
> this is when a COMMIT must be sent, the hope is that the server has
> already
> written the dirty pages to disk while the client was busy doing other
> things, and will respond with an OK quickly. If any dirty pages
> remain,
> they must be flushed prior to responding OK. Data should never be
> lost as
> long as the NFSPROC3_COMMIT procedure is adhered to.
>
Sure. This is how the Linux client works. The problem is the "async"
*export* option on the server.
--
Trond Myklebust <trond.myklebust@fys.uio.no>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-11-22 22:09 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 18:48 async vs. sync Lever, Charles
2004-11-22 15:36 ` Olaf Kirch
2004-11-22 17:55 ` jehan.procaccia
2004-11-22 18:06 ` Roger Heflin
2004-11-22 18:46 ` jehan.procaccia
2004-11-22 19:10 ` Roger Heflin
2004-11-22 21:44 ` jehan procaccia
2004-11-22 21:52 ` jehan procaccia
2004-11-22 22:20 ` Trond Myklebust
2004-11-22 22:57 ` jehan procaccia
2004-11-23 9:50 ` jehan procaccia
2004-11-23 14:57 ` J. Bruce Fields
2004-11-22 18:08 ` Trond Myklebust
2004-11-22 18:57 ` jehan.procaccia
2004-11-22 19:05 ` Roger Heflin
2004-11-22 20:14 ` Trond Myklebust
2004-11-22 21:04 ` Paul Cunningham
2004-11-22 21:14 ` Trond Myklebust
2004-11-22 22:07 ` Paul Cunningham [this message]
2004-11-22 22:26 ` Trond Myklebust
2004-11-22 22:34 ` Configuring NFS service for speed - " Neil Brown
2004-11-22 23:36 ` jehan procaccia
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 19:05 Lever, Charles
2004-11-23 16:36 Lever, Charles
2004-11-23 18:16 ` Dan Stromberg
2004-11-23 14:30 Lever, Charles
2004-11-23 21:46 ` jehan procaccia
2004-11-24 18:45 ` jehan.procaccia
2004-11-24 22:24 ` Neil Brown
2004-11-24 23:14 ` jehan procaccia
2004-11-24 23:34 ` Neil Brown
2004-11-24 22:09 ` Neil Brown
[not found] ` <Pine.GSO.4.53.0412010900500.5486@int1.cdc.noaa.gov>
2004-12-01 17:27 ` jehan.procaccia
2004-11-23 3:53 Lever, Charles
2004-11-23 16:33 ` Dan Stromberg
2004-11-22 22:14 Lever, Charles
[not found] <20041122214605.8E2B31D0FE1@sc8-sf-uberspam1.sourceforge.net>
2004-11-22 21:57 ` Joshua Baker-LePain
2004-11-22 21:50 Lever, Charles
2004-11-22 22:06 ` jehan procaccia
2004-11-23 1:09 ` Dan Stromberg
2004-11-22 19:02 Lever, Charles
2004-11-22 21:25 ` jehan procaccia
2004-11-22 21:45 ` Nicolas.Kowalski
2004-11-22 23:51 ` jehan procaccia
2004-11-22 18:31 Lever, Charles
2004-11-16 18:45 Lever, Charles
2004-11-16 16:15 Lever, Charles
2004-11-16 16:32 ` Trond Myklebust
2004-11-16 17:18 ` jehan.procaccia
2004-11-16 18:08 ` Trond Myklebust
[not found] <482A3FA0050D21419C269D13989C61130435E530@lavender-fe.eng.netapp.com>
2004-07-27 15:07 ` Bernd Schubert
2004-07-26 23:05 John Roberts
[not found] <482A3FA0050D21419C269D13989C61130435E523@lavender-fe.eng.netapp.com>
2004-07-26 21:28 ` Bernd Schubert
[not found] <482A3FA0050D21419C269D13989C61130435E51E@lavender-fe.eng.netapp.com>
2004-07-26 17:05 ` Bernd Schubert
2004-07-26 19:47 ` Jan Bruvoll
2004-07-26 22:06 ` Bernd Schubert
2004-07-27 12:00 ` Jan Bruvoll
2004-07-27 13:00 ` Bernd Schubert
2004-07-27 13:56 ` raven
2004-07-27 14:04 ` Jan Bruvoll
2004-07-27 14:11 ` Jan Bruvoll
2004-07-28 8:56 ` Olaf Kirch
2004-07-28 12:35 ` Bernd Schubert
2004-07-28 12:49 ` Olaf Kirch
2004-07-23 16:20 Linux NFS writes to Solaris very, very slow John Roberts
2004-07-26 15:17 ` async vs. sync Bernd Schubert
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='030901c4d0df$b9664bf0$2801a8c0@PAULLAPTOP1' \
--to=paulcunningham@sprintmail.com \
--cc=nfs@lists.sourceforge.net \
--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 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.