Date: Thu, 16 Mar 2006 18:10:09 -0500 From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: Mohan Srinivasan <mohan_srinivasan@yahoo.com> Cc: Rong-En Fan <grafan@gmail.com>, current@freebsd.org Subject: Re: unkillable process stuck in "nfsaio" Message-ID: <200603161810.09537.mi%2Bmx@aldan.algebra.com> In-Reply-To: <20060316225709.56198.qmail@web30813.mail.mud.yahoo.com> References: <20060316225709.56198.qmail@web30813.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
четвер 16 березень 2006 17:57, Mohan Srinivasan Ви написали:
> If you already have the 'intr' flag in fstab, then not being able
> to interrupt the operation on the mount is a bug. I'll take a look
> at it.
It is not in fstab, it is in amd.map -- the share is automounted:
/defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key}
* rhost!=${key};opts:=rw,grpid,resvport,vers=3,proto=udp,nosuid,nodev,intr
I thought, the `intr' flag is needed to be able to interrupt an operation
in case of a troublesome *server*.
In my case, the server is fine. It did not suddenly disconnect nor crash.
What I did was interrupt (with Ctrl-C) the program running on the client.
No, I do not have the corefile -- I rebooted :-(
Yours,
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603161810.09537.mi%2Bmx>