From: Jeff Garzik <jeff@garzik.org>
To: linux-nfs@vger.kernel.org
Cc: nfsv4@linux-nfs.org
Subject: NFS clients' use of fs_locations?
Date: Wed, 11 Feb 2009 15:00:50 -0500 [thread overview]
Message-ID: <49932E72.8060209@garzik.org> (raw)
According to the NFSv4 spec (section 6.1), regarding fs_locations,
On first access of the filesystem, the client should obtain the
value of the fs_locations attribute. If, in the future, the
client finds the server unresponsive, the client may attempt to
use another server specified by fs_locations.
Does any known client actually fail over to another fs_location, as
described here?
I am implementing the server side of this... AFAICT Linux barely uses
fs_locations, and Solaris just crashes.
Jeff
_______________________________________________
NFSv4 mailing list
NFSv4@linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
next reply other threads:[~2009-02-11 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 20:00 Jeff Garzik [this message]
2009-02-11 20:26 ` NFS clients' use of fs_locations? J. Bruce Fields
2009-02-11 21:17 ` Trond Myklebust
2009-02-11 21:30 ` Jeff Garzik
2009-02-11 21:53 ` 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=49932E72.8060209@garzik.org \
--to=jeff@garzik.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
/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.