From: "Wally Winchester" <wally_winchester@fastmail.fm>
To: nfs@lists.sourceforge.net
Subject: Stale nfs file handle - cwd without path - workaround?
Date: Mon, 16 Jan 2006 09:16:06 +0000 [thread overview]
Message-ID: <1137402966.3299.251938119@webmail.messagingengine.com> (raw)
Hello,
I have an nfs setup with heartbeat failover that is working nicely. I
only have one problem, I hope someone can help.
When nfs1 dies, and nfs2 takes over, everything works - as long as the
clients are writing files using the full paths.
If the path is omitted, i.e. they are expecting a write to their cwd, a
"stale nfs file handle" warning is issued.
Is there a way around this?
e.g. this works
touch /nfs-mount/file
(failover)
touch /nfs-mount/file
e.g. this doesn't work
cd /nfs-mount/
touch file
(failover)
touch file
(stale nfs file handle)
Thanks
--
Wally Winchester
wally_winchester@fastmail.fm
--
http://www.fastmail.fm - Access all of your messages and folders
wherever you are
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2006-01-16 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 9:16 Wally Winchester [this message]
2006-01-16 23:43 ` Stale nfs file handle - cwd without path - workaround? Bernd Schubert
2006-01-17 8:45 ` Wally Winchester
2006-01-18 18:18 ` Bernd Schubert
2006-01-23 13:23 ` Wally Winchester
2006-01-18 8:43 ` Wally Winchester
2006-01-18 21:05 ` Trond Myklebust
2006-01-27 11:32 ` [SOLVED] " Wally Winchester
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=1137402966.3299.251938119@webmail.messagingengine.com \
--to=wally_winchester@fastmail.fm \
--cc=nfs@lists.sourceforge.net \
/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.