Date: Thu, 28 Oct 1999 18:12:29 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: freebsd-current@freebsd.org Subject: odd NFS behaviour with DU 4.F client Message-ID: <14360.50663.727201.679421@grasshopper.cs.duke.edu>
next 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 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 in this filesystem, the DU4CLIENT mounts it & I see this transaction: 18:00:27.725678 DU4CLIENT.1435222468 > FREEBSDSERVER.nfs: 168 lookup fh 234,2/163298400 "chase" (ttl 30, id 9546) 18:00:27.725763 FREEBSDSERVER.nfs > DU4CLIENT.1435222468: reply ok 236 lookup fh 234,2/163298400 DIR 755 ids 1449/107 sz 1024 nlink 21 rdev 134/57475167 fsid 86036d005f nodeid 36d005f00000000 a/m/ctime 941102013.000000 940944335.000000 940944335.000000 post dattr: DIR 775 ids 0/107 sz 512 nlink 25 rdev 4/40 fsid 400000028 nodeid 2800000000 a/m/ctime 941134393.000000 940612206.000000 940612206.000000 (ttl 64, id 16062) 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 ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 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?14360.50663.727201.679421>