Date: Tue, 15 Apr 1997 22:09:41 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!freebsd.org!FreeBSD-gnats-submit Subject: kern/3304: NFS V2 readdir hangs Message-ID: <199704160209.WAA01541@lakes.water.net> Resent-Message-ID: <199704160500.WAA09528@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 3304 >Category: kern >Synopsis: NFS V2 readdir hangs >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 15 22:00:01 PDT 1997 >Last-Modified: >Originator: Thomas David Rivers >Organization: SAS Institute >Release: FreeBSD 2.2.1-STABLE i386 >Environment: FreeBSD 2.2.1 - downloaded from ftp.freebsd.org on April 8th. >Description: NFS readdir can hang when accessing V2 servers. Further access the mounted file system is blocked... It appears that an nfs_send() is issued to continue reading the directory; following by an nfs_receive() which eventually (via soreceive) blocks in sbwait(), waiting on a packet that never arrives. It's not at all clear to me (personally) if this is a problem with the NFS protocol (i.e. we've sent, and are waiting on a response from, an invalid NFS request) - or some underlying problem with soreceive(). >How-To-Repeat: Mount a V2 NFS server (I've tried both Sunos 4.1.3 and HP/UX 9.05), go to a rather large directory and do "ls -l". The ls -l will hang in sbwait(). This apparently also needs a rather slow network for a reliable reproduction - that is, it's somewhat timing dependent. >Fix: Unknown at this point. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704160209.WAA01541>