kern/68698: vinum(4) broken in 5.2-current

Greg 'groggy' Lehey grog at
Wed Jul 7 16:40:23 PDT 2004

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

From: Greg 'groggy' Lehey <grog at>
To: Matthias Schuendehuette <msch at>
Cc: freebsd-gnats-submit at
Subject: Re: kern/68698: vinum(4) broken in 5.2-current
Date: Thu, 8 Jul 2004 09:02:38 +0930

 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 On Wednesday,  7 July 2004 at 21:17:41 +0200, Matthias Schuendehuette wrote:
 > On Tuesday 06 July 2004 00:52, Greg 'groggy' Lehey wrote:
 >> Please supply details of the panic.
 > Yes, it took some time to write all down from the screen
 > but here it is...
 > [...]
 > Pre_seeding PRNG: kickstart.
 > Loading configuration files.
 > Entropy harvesting: interrupts ethernet point_to_point kickstart.
 > panic: unmount: dangling vnode
 > Debugger ("panic")
 > Stopped at  Debugger+0x4f:  xchgl  %ebx,in_Debugger.0
 > db> trace
 > Debugger(c072edc1,c07c9aa0,c0732ebc,cc5a6944,100) at Debugger+0x4f
 > panic(c0732ebc,cc5a6984,cc5a6984,cc5a69e0,c05be735) at panic+0x150
 > vfs_nmount(c1630800,c15269a0,c15269a0,c15269a0,cc5a6970) at vfs_nmount+0x
 > getdiskbyname(c1701900,1,c05b3100,140,61) at getdiskbyname+0x95
 > open_drive(c1701900,c15269a0,0,c1701900,cc5a6a40) at open_drive+0x1e
 > init_drive(c1701900,0,1,c089c177,c1708800) at init_drive+0x2b
 > read_drive_label(c1701900,0,cc5a6a88,c057f3c6,1) at read_drive_label+0x22
 > check_drive(c1708800,408,c08a9f61,1,61) at check_drive+0x50
 > vinum_scandisk(c1625d40,c13d45e8,1000040,c1707000,c1781840) at vinum_scandisk+0x187
 > vinum_super_ioctl(c16ebe00,c400464b,c1707000,3,c15269a0) at vinum_super_ioctl+0x436
 > spec_ioctl(cc5a6b80,cc5a6c2c,c05d026d,cc5a6b80,c06e0c45) at spec_ioctl+0x185
 > spec_vnoperate(cc5a6b80,c06e0c45,c1506900,28143000,cc5a6b90) at spec_vnoperate+0x18
 > vn_ioctl(c175350c,c400464b,c1707000,c14f8d80,c15269a0) at vn_ioctl+0xad
 > ioctl(c15269a0,cc5a6d14,c,cc5a6d48,3) at ioctl+0x137
 > syscall(2f,2f,2f,0,1) at syscall+0x1d0
 > Xint80_syscall() at Xint80_syscall+0x1f
 > - --- syscall(54, FreeBSD ELF32, ioctl), eip = 0x2814f16f, esp = 0xbfbfe52c, ebp = 0xbfbffe958 ---
 > db> reset
 A ddb stack trace is barely helpful.  As stated at, we really need a dump.
 > Perhaps it is more a GEOM-Problem triggered by vinum, but I'm only
 > an interested admin...
 But you're running -CURRENT, which is for developers only.
 Note: I discard all HTML mail unseen.
 Finger grog at for PGP public key.
 See complete headers for address and phone numbers.
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 Version: GnuPG v1.2.0 (FreeBSD)

More information about the freebsd-bugs mailing list