All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Random ESTALE due to lookup "/" in mount point?
Date: Wed, 23 Aug 2006 17:09:41 +0200	[thread overview]
Message-ID: <20060823150941.GA13000@janus> (raw)

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:

   16:42:03.644621 IP 172.17.1.64.3759242568 > 172.17.1.1.2049: 120 lookup fh 2956,259248/28524 "stat"
   16:42:03.644967 IP 172.17.1.1.2049 > 172.17.1.64.3759242568: reply ok 116 lookup ERROR: No such file or directory
   16:42:03.647345 IP 172.17.1.64.3776019784 > 172.17.1.1.2049: 112 getattr fh 2956,259248/2
   16:42:03.647496 IP 172.17.1.1.2049 > 172.17.1.64.3776019784: reply ok 112 getattr DIR 1777 ids 0/0 sz 0x2000
=> 16:42:03.648002 IP 172.17.1.64.3792797000 > 172.17.1.1.2049: 120 lookup fh 2956,259248/2 "/"
   16:42:03.648244 IP 172.17.1.1.2049 > 172.17.1.64.3792797000: reply ok 116 lookup ERROR: No such file or directory
   16:42:03.648440 IP 172.17.1.64.3809574216 > 172.17.1.1.2049: 112 getattr fh 2956,259248/2
   16:42:03.648680 IP 172.17.1.1.2049 > 172.17.1.64.3809574216: reply ok 112 getattr DIR 1777 ids 0/0 sz 0x2000
=> 16:42:03.648877 IP 172.17.1.64.3826351432 > 172.17.1.1.2049: 120 lookup fh 2956,259248/2 "/"
   16:42:03.649110 IP 172.17.1.1.2049 > 172.17.1.64.3826351432: reply ok 116 lookup ERROR: No such file or directory
   16:42:09.605452 IP 172.17.1.64.3879531864 > 172.17.1.1.2049: 116 access fh 3806,805074/16337 001f
   16:42:09.605758 IP 172.17.1.1.2049 > 172.17.1.64.3879531864: reply ok 120 access c 001f

-- 
Frank

-------------------------------------------------------------------------
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

             reply	other threads:[~2006-08-23 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 15:09 Frank van Maarseveen [this message]
2006-08-23 16:20 ` Random ESTALE due to lookup "/" in mount point? Trond Myklebust
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=20060823150941.GA13000@janus \
    --to=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 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.