From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Vsevolod (Simon) Ilyushchenko" <simonf@cshl.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: Failover using wackamole?
Date: Mon, 28 Feb 2005 14:21:01 -0500 [thread overview]
Message-ID: <20050228192101.GD21364@fieldses.org> (raw)
In-Reply-To: <42234450.9070004@cshl.edu>
On Mon, Feb 28, 2005 at 11:18:24AM -0500, Vsevolod (Simon) Ilyushchenko wrote:
> I had this neat idea that NFS failover of read-only filesystems can be
> achieved using wackamole (floating IP adresses providing very simple
> HA). This did not work with NFS 3 because the filehandles are different
> on the primary and the secondary servers, so I was getting a "stale NFS
> filehandle" error after the failover.
>
> I tried this using NFS 4 nfs-utils-1.0.6-52 from FC3 updates. However,
> it still failed with the following error:
> ls: reading directory a: Input/output error
> and this in the error log on the client:
> kernel: RPC: garbage, exit EIO
>
> Is this a bug or a feature?
Hm, there may be a bug there. But in any case v4 isn't going to help
you here. It's constructing filehandles in exactly the same was as v3.
--b.
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-28 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 16:18 Failover using wackamole? Vsevolod (Simon) Ilyushchenko
2005-02-28 19:21 ` J. Bruce Fields [this message]
2005-02-28 20:24 ` Vsevolod (Simon) Ilyushchenko
2005-02-28 20:34 ` J. Bruce Fields
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=20050228192101.GD21364@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=simonf@cshl.edu \
/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.