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

Matthias Schuendehuette msch at
Wed Jul 7 12:20:36 PDT 2004

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

From: Matthias Schuendehuette <msch at>
To: "Greg 'groggy' Lehey" <grog at>
Cc: freebsd-gnats-submit at
Subject: Re: kern/68698: vinum(4) broken in 5.2-current
Date: Wed, 7 Jul 2004 21:17:41 +0200

 Hash: SHA1
 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...
 In the meantime I switched to a current 'current'-kernel,
 cvsup-ed around Wed Jul  7 13:16:20 UTC 2004, ACPI is enabled,
 SCHED_ULE is used, the system has two 'sym' SCSI-controllers
 with 5 disks and a lonesome IBM-DTLA-307045 IDE-disk.
 The funny thing is, that vinum still triggers a panic,
 but it is possible to start vinum after the system has come up.
 But here now the trace from the panic:
 =2D -------------------8><----------------------------------------
 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_scandi=
 vinum_super_ioctl(c16ebe00,c400464b,c1707000,3,c15269a0) at vinum_super_ioc=
 spec_ioctl(cc5a6b80,cc5a6c2c,c05d026d,cc5a6b80,c06e0c45) at spec_ioctl+0x185
 spec_vnoperate(cc5a6b80,c06e0c45,c1506900,28143000,cc5a6b90) at spec_vnoper=
 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
 =2D --- syscall(54, FreeBSD ELF32, ioctl), eip =3D 0x2814f16f, esp =3D 0xbf=
 bfe52c, ebp =3D 0xbfbffe958 ---
 db> reset
 =2D -------------------8><----------------------------------------
 Perhaps it is more a GEOM-Problem triggered by vinum,
 but I'm only an interested admin...
 If further informations are needed let me know.
 Thank you so far - Matthias
 =2D --=20
 Ciao/BSD - Matthias
 Matthias Schuendehuette	<msch [at]>, Berlin (Germany)
 PGP-Key at <> and <> ID: 0xDDFB0A5F
 Version: GnuPG v1.2.4 (FreeBSD)

More information about the freebsd-bugs mailing list