Date: Tue, 20 Jun 2000 08:13:14 -0500 (CDT) From: David Scheidt <dscheidt@enteract.com> To: Elias Athanasopoulos <eatha@cc.uoa.gr> Cc: freebsd-hackers@freebsd.org Subject: Re: NFS client locks. Message-ID: <Pine.NEB.3.96.1000620080904.35544A-100000@shell-1.enteract.com> In-Reply-To: <20000621131241.A967@neutrino.uoa.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96.1000620080904.35544A-100000>