Date: Thu, 28 Oct 1999 15:25:00 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client Message-ID: <199910282225.PAA12530@apollo.backplane.com> References: <14360.50663.727201.679421@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
:We have an NFS server setup running an older FreeBSD-current (Wed Jun 30).
:This server exports a filesystem to a number of heterogenous clients.
:On most clients, this filesystem is automounted.
:
:Occasionally, some random Digital UNIX box running 4.0F will partially
:wedge because it's automounter is blocked accessing the FreeBSD
Lots of bugs have been fixed since then. I recommend upgrading the
server (despite the hassle) and seeing if the problem still occurs.
:server's filesystem. Any access to automounted directories will then
:cause a process to hang.
:
:I've noticed that if I do a tcpdump on the FreeBSD NFS server, I see:
:
:17:48:16.397101 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4256)
:17:48:36.397144 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4310)
:17:48:56.397212 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4384)
:17:49:16.397123 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4453)
:
:These requests go on seemingly forever with no reply from the FreeBSD
:NFS server. "chase" is a users' directory in the top level of this
:filesystem, and nfsfilesystem/chase/bin is a component of the user
:chase's path.
:...
:The truely interesting thing is that if I type 'mount' on DU4CLIENT, I
:DO NOT see the filesystem in question in the mount table!
:
:If I kill all of chase's process on DU4CLIENT, the automounter
:unsticks and all is well. If I then try to access the chase directory
Well, there was a bug in nfsrv_create() which caused the server to
not reply to an NFS packet. This led to a general revamping of the
server side code which may have fixed other rpc's at the same time.
Whether fixing that bug solves the problem you are having or not is
unknown.
:I would guess that the DU4CLIENT has the filehandle cached somewhere,
:even though it has unmounted the filesystem.
:
:My question: Whose fault is this? Should the FreeBSD server be
:ignoring requests to a valid filehandle if the client has not mounted
:the FS? Should it be returning some sort of error?
:
:Thanks,
:
:Drew
There should be a response to the rpc either way so my guess is that
it is a server-side bug.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910282225.PAA12530>