From: Mark Lehrer <mark@tpsit.com>
To: linux-nfs@vger.kernel.org
Subject: Time to declare war on "stale nfs file handle"
Date: Tue, 19 Feb 2013 15:36:25 -0700 (MST) [thread overview]
Message-ID: <alpine.DEB.1.00.1302191507240.5816@shell> (raw)
I set up a pair of servers with DRBD, Pacemaker, and a virtual IP address. I am mounting with NFSv3 & TCP. The /etc/exports entry looks like this:
/nfs/volume01 *(rw,no_root_squash,fsid=778,insecure,async)
Failing between nodes seems to work well whenever I am testing it.
However, it seems that whenever I get into a situation where it has
been running for awhile and then I fail over, clients get the dreaded
Stale NFS file handle error on any open files. In this case they are
VM images, which means lots of rebooting.
What should I do to prevent this error from happening? I didn't have any
luck with exportfs -f. Unfortunately this is a tough one to duplicate so
I am just trying to prepare a few tests for the next time it happens.
Also, I understand that NFSv4 is not quite as stateless as the older versions.
Will this kind of arrangement have potential data loss issues on NFSv4?
Thanks,
Mark
next reply other threads:[~2013-02-19 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 22:36 Mark Lehrer [this message]
2013-02-20 20:21 ` Time to declare war on "stale nfs file handle" J. Bruce Fields
2013-02-21 21:01 ` Mark Lehrer
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=alpine.DEB.1.00.1302191507240.5816@shell \
--to=mark@tpsit.com \
--cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox