Date: Sat, 21 Oct 2006 01:22:49 -0600 From: John E Hein <jhein@timing.com> To: David Xu <davidxu@freebsd.org> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-stable@freebsd.org, jhb@freebsd.org Subject: Re: locked vnode / nfs... requires kill -9 in ddb Message-ID: <17721.51913.929897.898519@gromit.timing.com> In-Reply-To: <200610211510.09350.davidxu@freebsd.org> References: <17718.20457.799395.602805@gromit.timing.com> <20061021035749.GY55428@deviant.kiev.zoral.com.ua> <17721.50338.220767.201120@gromit.timing.com> <200610211510.09350.davidxu@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David Xu wrote at 15:10 +0800 on Oct 21, 2006: > On Saturday 21 October 2006 14:56, John E Hein wrote: > > > David, here's the original report. > > http://lists.freebsd.org/pipermail/freebsd-stable/2006-October/029755.html > > > > Indeed, as Kostik surmised, the mount point is mounted intr. > > > > I did not notice this problem while running with releng_6 from late > > June for 3 months. Could it be this problem was introduced between > > then and now? > > > > This also just happened today on a system I just updated from 5.3 > > to 5.5-p8. > > This is also RELENG_4's behavior, if PCATCH is set, the tsleep will > call CURSIG() which will suspends current process if there is a > SIGTSTP or SIGSTOP signal. Great. Suspending the process is what I expect when I hit ctrl-z. Hanging access to the filesystem isn't. ;) Nor have I had this problem when running 4.11
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17721.51913.929897.898519>