Subject: Re: kern/21423
To: Chuck Silvers <firstname.lastname@example.org>
From: Ed Ravin <email@example.com>
Date: 01/07/2006 17:17:35
On Sun, Nov 06, 2005 at 11:51:55AM -0800, Chuck Silvers wrote:
> the first release that had that fix was 2.0.2.
> 2.1 also had it, as will 3.0.
21423 is still with us - we just tried to reboot a NetBSD 2.0.3 box that
had a bad NFS mount (the server was down) with "shutdown -r", and it got
stuck in the usual place (after the "Shutting down..." message but before
"Rebooting..."). I had to get into the kernel debugger and issue "reboot 0x4"
to get the reboot to proceed.
Also, it's unclear to me how the problem in 28971 (a problem in readdir)
could be related to the inability to unmount a bad NFS mount.
> On Sun, Nov 06, 2005 at 02:38:49PM -0500, Ed Ravin wrote:
> > On Sun, Nov 06, 2005 at 06:35:00PM +0000, firstname.lastname@example.org wrote:
> > > Synopsis: kernel cannot reboot when process locked in NFS I/O
> > >
> > > State-Changed-From-To: open->feedback
> > > State-Changed-By: email@example.com
> > > State-Changed-When: Sun, 06 Nov 2005 18:34:59 +0000
> > > State-Changed-Why:
> > > I believe this was the same problem that you reported again in PR 28971,
> > > which has been fixed. can you confirm this?
> > I don't think we ever started using the fix for 28971 - we're still using 2.0
> > on most of our machines. Did Takashi's pullup request #1208 (see below, from
> > our correspondence on PR 28971) ever get into 2.0, and if so, when?
> > > > Thanks! I see the fix was in nfs_vnops.c - it doesn't like it's
> > > > been pulled into the 2.0 branch, which is what we're running.
> > >
> > > i've sent a pullup request. (#1208)
> > > no idea when it will be processed, though.
> > >
> > > YAMAMOTO Takashi