Subject: Re: kern/37034: Processes stuck on vnlock: accessing msdos fs mounted
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: rudolf <netbsd@eq.cz>
List: netbsd-bugs
Date: 09/28/2007 14:40:02
The following reply was made to PR kern/37034; it has been noted by GNATS.

From: rudolf <netbsd@eq.cz>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/37034: Processes stuck on vnlock: accessing msdos fs mounted
 from img (vnconfig)
Date: Fri, 28 Sep 2007 16:35:16 +0200

 Antti Kantee wrote:
 >  On Fri Sep 28 2007 at 10:30:09 +0000, rudolf wrote:
 >  >  I also forget to mention in the report that the filesystem in the img is 
 >  >  slightly corrupted. I don't know if this could cause this problem, under 
 >  >  Linux I can access the fs, just not each file in it.
 >  
 >  Yes, that would likely be the cause.  If you can share the image, that
 >  would be great.
 
 No problem, but it is quite big: 16 GB uncompressed. If you'll need it, 
 we can arrange it somehow.
 
 >  Meanwhile, try if this helps:
 [...]
 
 With this patch I could do 'ls -al /top_of_msdosfs/', 'find 
 /top_of_msdosfs/', ... and everything was ok. Then 'shutdown -r now' 
 caused this panic:
 
 syncing disks... done
 unmounting file systems...
 unmounting /mnt2 (/dev/vnd0a)... vrele: bad ref count: tag VT_UFS(1) 
 type VBLK(3), usecount -1, writecount 0, refcount 1858, flags(0<LOCKSWORK>)
 tag VT_UFS, ino 184765, on dev 0, 32 flags 0x0, effnlink 1, nlink 1
 mode 060640, owner 0, group 5, size 0 not locked
 panic: vrele: ref cnt vp 0xffff80004c203e20
 Stopped in pid 60.1 (reboot) at netbsd:cpu_Debugger+0x5: leave
 
 I have a core dump from this one too.
 
 r.