lkml.org 
[lkml]   [1997]   [Jan]   [11]   [last100]   RSS Feed
Views: [more markup]   [less markup]   [headers]   [forward]  
 
Messages in this thread
/
From(Miquel van Smoorenburg)
SubjectRe: nfs deadlock problem in kernel 2.0.27 ?
Date11 Jan 1997 20:14:36 +0100
In article <Pine.LNX.3.95.970111075859.11593C-100000@zen.via.ecp.fr>,
Michel LESPINASSE  <walken@via.ecp.fr> wrote:
>I had a problem twice with the 2.0.27 kernel, I think this is a bug in the
>nfs filesystem code.
>When accessing remote filesystems, it sometimes happens that the reading
>process gets locked. I think that it is locked inside the kernel, because
>it is impossible to kill -9 it.

That might also mean that the remote NFS server is not responding anymore.
That's how NFS works; if the server goes away everything hangs until it
comes back.

>8:31 [root:2] Studio:~# lsof /mnt/debian
>COMMAND     PID     USER   FD   TYPE     DEVICE   SIZE/OFF      INODE NAME
>zcat       2685     root    0r   REG     0,   2     158525  556423252
>/mnt/debian (bouddha:/debian)
>
>[the inode number seems much too big.... is this the reason for the bug
>or the consequence of it ?]

Nope that's because it's NFS.

>This nfs partition is mounted at boot-time with this entry in my fstab :
>bouddha:/debian /mnt/debian nfs defaults,nodev,noexec,nosuid,rsize=8192,ro 

Try adding the option "intr"

Mike.
-- 
|  Miquel van Smoorenburg    | "Sticky tape is like the Force - it has a   |
| miquels@drinkel.cistron.nl |  dark side, it has a light side, and it     |
| ----8<--------------8<---- |  holds the universe together" - Carl Zwanig |

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:1.077 / U:2.210 seconds]
©2003-2008 Jasper Spaans