Re: NFS client locks.
On Tue, 20 Jun 2000, David Scheidt wrote: > 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 Thanx for all your answers. I should have first checked the NFS related papers. Regards, Elias -- Elias Athanasopoulos | I bet the human brain is | H.E.P & Apps. Lab. http://www.uoa.gr/~eatha | a kludge. -Marvin Minsky | University Of Athens To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NFS client locks.
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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
NFS client locks.
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 configuration constants seem perfectly resonable. I would like to help solving the problem, if it is an actual one. Otherwise, my apologies for taking your time. FreeBSD box: FreeBSD gluon.particles.org 5.0-2406-CURRENT FreeBSD 5.0-2406-CURRENT #0: Thu Apr 6 13:52:15 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 Regards, Elias -- Elias Athanasopoulos | I bet the human brain is | H.E.P & Apps. Lab. http://www.uoa.gr/~eatha | a kludge. -Marvin Minsky | University Of Athens To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message