From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: przemyslaw_sowa@o2.pl
Cc: nfs@lists.sourceforge.net
Subject: Re: NFSv3 and SYNC option
Date: Mon, 17 Jul 2006 08:05:05 -0400 [thread overview]
Message-ID: <1153137905.5835.11.camel@localhost> (raw)
In-Reply-To: <20060717091137.62C9221400D@rekin14.go2.pl>
On Mon, 2006-07-17 at 11:11 +0200, przemyslaw_sowa@o2.pl wrote:
> Hello,
>
> I'd like to know if the "sync" option in /etc/exports makes NFSv3 works
> like NFSv2? I mean if it then always waits for the data to be written to
> the drive before sending reply?
No. The 'sync' option just ensures that all RPC calls that require data
to be put to stable storage are honoured. The result is that you should
be guaranteed correct recovery semantics in case of a server
crash/reboot (which is what you want).
> If not, is there any way to guarantee stable storage on the server (v3)
> side (ex. client can mount with the async option)?
Yes. NFSv3 has protocol support for safe server-side cached writes (this
is the main reason why NFSv3 is considered to be faster than NFSv2). By
"safe", I mean that there is no loss of data in the case of a server
crash/reboot.
This caching behaviour is enabled by default: no need for additional
mount options.
Cheers,
Trond
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-07-17 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 9:11 NFSv3 and SYNC option przemyslaw_sowa
2006-07-17 12:05 ` Trond Myklebust [this message]
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=1153137905.5835.11.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=przemyslaw_sowa@o2.pl \
/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.