netbsd-bugs@netbsd.org
[Top] [All Lists]

Re: kern/40163: mv(1) cause WAPBL panic

Subject: Re: kern/40163: mv(1) cause WAPBL panic
From: Greg Oster
Date: Sun, 14 Dec 2008 03:45:19 UTC
Newsgroups: fa.netbsd.bugs

The following reply was made to PR kern/40163; it has been noted by GNATS.

From: Greg Oster <oster@xxxxxxxxxxx>
To: gnats-bugs@xxxxxxxxxx
Cc: 
Subject: Re: kern/40163: mv(1) cause WAPBL panic 
Date: Sat, 13 Dec 2008 21:40:37 -0600

 David Holland writes:
 > The following reply was made to PR kern/40163; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs@xxxxxxxxxx>
 > To: Lloyd Parkes <lloyd@xxxxxxxxxxxxxxxxxxxxxxx>
 > Cc: dholland@xxxxxxxxxx, gnats-admin@xxxxxxxxxx, netbsd-bugs@xxxxxxxxxx,
 >      gnats-bugs@xxxxxxxxxx
 > Subject: Re: kern/40163: mv(1) cause WAPBL panic
 > Date: Sun, 14 Dec 2008 03:22:14 +0000
 > 
 >  On Sat, Dec 13, 2008 at 06:10:05AM +0000, Lloyd Parkes wrote:
 >   >> Untested (I don't have any wapbl volumes on hand) patch:
 >   >  
 >   >  Not untested anymore. The patch seems to have fixed the problem, and  
 >   >  I get the same error message from NetBSD as I do from other systems,  
 >   >  so the error path can't be too far wrong.
 >  
 >  Can you still unmount the fs afterwards? :-)
 
 I can..
 
 >  (Anything wrong would almost certainly be vnode refcounting.)
 >  
 >  Did you (or anyone else listening) test it on 5.0? I need to file a
 >  pullup, and while there should be no reason for it to behave
 >  differently on 5.0, everything connected with rename is so bodgy that
 >  I'd like some positive confirmation. And I don't currently have a 5.0
 >  machine.
 
 I applied your changes to a 5.0_BETA tree and tested using that.
 I've also just run a fsck on the filesystem (it's been mounted and
 unmounted dozens of times since the first check) and it's showing 
 everything as clean.
 
 Later...
 
 Greg Oster
 
 

<Prev in Thread] Current Thread [Next in Thread>