From: "Lever, Charles" <Charles.Lever@netapp.com>
To: "Timothy G. Wesemann" <timwese@voicenet.com>
Cc: <nfs@lists.sourceforge.net>
Subject: RE: nfs: server X not responding, still trying
Date: Tue, 4 Nov 2003 08:34:14 -0800 [thread overview]
Message-ID: <482A3FA0050D21419C269D13989C6113020AC622@lavender-fe.eng.netapp.com> (raw)
it was pointed out to me that this was not entirely clear:
> > The client mount/fstab options are:
> > "rw,async,intr,vers=3D3,rsize=3D32768,wsize=3D32768" and the=20
> > server's exports
> > options are: "rw,no_root_squash,async,no_subtree_check".
>=20
> i am obligated to provide a friendly warning about using
> the "async" export option. see the Linux NFS FAQ
> (http://nfs.sourceforge.net) for details.
>=20
> the async mount option is not needed, as async is the default.
the async export option is to be avoided.
^^^^^^
the async mount option is superfluous.
^^^^^
especially with NFSv3, async in either place is really not
necessary. the Linux NFS FAQ has some explanatory text that
details why this is the case.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-11-04 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 16:34 Lever, Charles [this message]
2003-11-05 18:03 ` nfs: server X not responding, still trying Timothy G. Wesemann
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 22:50 Lever, Charles
2003-11-04 16:08 Lever, Charles
2003-11-03 22:35 Timothy G. Wesemann
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=482A3FA0050D21419C269D13989C6113020AC622@lavender-fe.eng.netapp.com \
--to=charles.lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=timwese@voicenet.com \
/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.