From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: Random ESTALE due to lookup "/" in mount point?
Date: Wed, 23 Aug 2006 12:20:25 -0400 [thread overview]
Message-ID: <1156350025.5619.14.camel@localhost> (raw)
In-Reply-To: <20060823150941.GA13000@janus>
On Wed, 2006-08-23 at 17:09 +0200, Frank van Maarseveen wrote:
> NFSv3, udp, client=2.6.17.8, server=tru64
>
> On the client I started to get some random ESTALE errors which disappeared
> quickly afterwards without a remount. The errors only occurred when typing
>
> stat ..
>
> in a subdirectory of a mountpoint. Doing ls -al in that subdirectory
> gave an ESTALE only on "..". I could even change directory to / and back
> without an ESTALE but the "stat .." command still gave an ESTALE.
>
> A "tcpdump -i eth0 udp port 2049 -n -s 1500" showed something which is
> unusual to my knowledge. The kernel tried to lookup "/" in the mount
> point as it seems:
I've never seen that, and my own kernel certainly appears to do no such
thing when I stat '..'.
Any chance of a 'strace' with that?
Cheers,
Trond
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-08-23 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 15:09 Random ESTALE due to lookup "/" in mount point? Frank van Maarseveen
2006-08-23 16:20 ` Trond Myklebust [this message]
2006-08-24 23:19 ` Frank van Maarseveen
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=1156350025.5619.14.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=frankvm@frankvm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox