[lkml]   [2001]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [bug report] NFS and uninterruptable wait states
Peter Wächtler wrote:
> Phillip Susi wrote:
> >
> [ "mount -tnfs" with hard has default ]
> > Anyhow, about an hour later ( the mount process still stuck ) I figured out
> > that the other machine was not running rpc.nfsd, though it was running
> > rpc.mountd. Once I started rpc.nfsd on the machine, the mount on my box
> > finally returned ( and was terminated by the SIGKILL that I sent it an hour
> > before ).
> >
> > Could someone confirm that this is a bug, and explain why anything should
> > ever need to wait in that state?
> >
> Well, if you use the option "soft",then your process is interruptible.
> From a user standpoint, I don't understand the requirement of 'D' state.
> Where this gets really impractical: commands like df or du will
> hang forever (if the other end is out of your control).

Err, "intr" will give you interruptible state. "hard" will retry forever,
"soft" will timeout and give up .

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:01    [W:0.120 / U:1.892 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site