From: "Chandan S Pansare \(pcsbom\)" <chandan.pansare@patni.com>
To: <linux-kernel@vger.kernel.org>
Subject: kernel enhancement for stale NFS file handle?
Date: Fri, 9 May 2003 19:26:11 +0530 [thread overview]
Message-ID: <00b401c31632$d19b7d30$f1bba5cc@pc5579> (raw)
Hi,
I am trying to configure Veritas Cluster server on RHAS2.1 (2 node
configuration). Every thing works fine till I configure NFS service group.
Once the service is up I am able to mount exported FS on my client machine.
But once I switch over the service from one node to another, I get *stale
NFS file handle* error for any open file (eg while doing dd if=/dev/zero
of=<mntd_FS>/<file> I get stale handle for <file>) but I am able to do any
new operation like ls, cd or dd without any need for unmounting/mounting the
FS.
This requires some kernel enhancement and is implemented in RHAS2.1 (kernel
2.4.9-e.3) but still I am facing this problem.
I had same trouble with RED HAT CLUSTER MANAGER but somehow it got resolved.
[ and I am not sure how :-( ]
Any idea how this can be resolved??
Regards
Chandan
reply other threads:[~2003-05-09 13:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='00b401c31632$d19b7d30$f1bba5cc@pc5579' \
--to=chandan.pansare@patni.com \
--cc=linux-kernel@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