From: Jeff Garzik <jeff@garzik.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: NFS clients' use of fs_locations?
Date: Wed, 11 Feb 2009 16:30:04 -0500 [thread overview]
Message-ID: <4993435C.2090903@garzik.org> (raw)
In-Reply-To: <1234387040.7423.287.camel@heimdal.trondhjem.org>
Trond Myklebust wrote:
> On Wed, 2009-02-11 at 15:00 -0500, Jeff Garzik wrote:
>> 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.
>
> Hi Jeff,
>
> I'm working on finishing the migration code, and expect to have it ready
> soon.
Neat! Will that include the simple fail-over actions described above?
> Until that, though, Bruce's suggestion of AIX is probably your best bet.
> AFAIK, they've had migration support in their client for several years.
Thanks! Any idea at all if AIX client supports fail-over, or simply
migration based on NFS4ERR_MOVED?
Time to figure out how to access AIX NFS client...... :)
Jeff
next prev parent reply other threads:[~2009-02-11 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 20:00 NFS clients' use of fs_locations? Jeff Garzik
2009-02-11 20:26 ` J. Bruce Fields
2009-02-11 21:17 ` Trond Myklebust
2009-02-11 21:30 ` Jeff Garzik [this message]
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=4993435C.2090903@garzik.org \
--to=jeff@garzik.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--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.