From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>, nfs@lists.sourceforge.net
Subject: 2.6.9-rc1 bk-current v2 mount "stale file handle" problems
Date: Sat, 28 Aug 2004 12:44:20 -0700 [thread overview]
Message-ID: <4130E094.1010309@backtobasicsmgmt.com> (raw)
I just upgraded two of my boxes here to 2.6.9-rc1 pulled from BitKeeper
a few hours ago. One of them is my NFS server, using the kernel NFS
daemon and serving XFS filesystems. The other is an NFS root client,
using the kernel's autoconfiguration and NFS root mounting (using all
default mount options).
After booting the NFS client, I had very strange behavior when creating
symlinks on the NFS root if the link target path began with '.'. Just
this sequence:
# mkdir foo
# cd foo
# ln -sf . test1
# ln -sf . test2
...
Would result in a successfully created link but an error message from ln
reporting "stale NFS file handle".
Switching the NFS root client's mount to v3 from v2 seems to have
avoided the problem.
next reply other threads:[~2004-08-28 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 19:44 Kevin P. Fleming [this message]
2004-08-28 19:56 ` 2.6.9-rc1 bk-current v2 mount "stale file handle" problems William Lee Irwin III
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=4130E094.1010309@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=linux-kernel@vger.kernel.org \
--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.