From owner-freebsd-hackers Tue Jun 20 6:13:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 7407237BE9E for ; Tue, 20 Jun 2000 06:13:41 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id IAA66248; Tue, 20 Jun 2000 08:13:14 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Tue, 20 Jun 2000 08:13:14 -0500 (CDT) From: David Scheidt To: Elias Athanasopoulos Cc: freebsd-hackers@freebsd.org Subject: Re: NFS client locks. In-Reply-To: <20000621131241.A967@neutrino.uoa.gr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jun 2000, Elias Athanasopoulos wrote: :Hi, : :I have a Linux box as an NFS server and a FreeBSD box which acts as an :NFS client. If I explicitly shutdown the NFS services in the Linux box, :actions like 'df', 'ls /mnt' (/mnt is the mount point of the remote :directory), or even 'umount /mnt', in the FreeBSD box, seem to lock forever. :I waited for about 20-25 mins, I got a 'server not responding' message, but :the processes were still locked and I could not even kill them. : :I started again the NFS services in the Linux box and I got a 'server alive' :message in the FreeBSD box, after about 10 mins. : :Is that the correct behaviour? I had a look over /sys/nfs/nfs.h and the Yep. That's the expected behavior. If this is a problem, you can use the intr to make processes blocked on I/O to the missing filesystems interruptible. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message