From nobody@FreeBSD.org  Mon Jul  5 14:45:51 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 41FF016A4CF
	for <freebsd-gnats-submit@FreeBSD.org>; Mon,  5 Jul 2004 14:45:51 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3C60743D60
	for <freebsd-gnats-submit@FreeBSD.org>; Mon,  5 Jul 2004 14:45:51 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i65EjpPa022559
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 5 Jul 2004 14:45:51 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i65EjpqV022558;
	Mon, 5 Jul 2004 14:45:51 GMT
	(envelope-from nobody)
Message-Id: <200407051445.i65EjpqV022558@www.freebsd.org>
Date: Mon, 5 Jul 2004 14:45:51 GMT
From: Matthias Schuendehuette <msch@snafu.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: vinum(4) broken in 5.2-current
X-Send-Pr-Version: www-2.3

>Number:         68698
>Category:       kern
>Synopsis:       [vinum] vinum(4) broken in 5.2-current
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    le
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul 05 14:50:20 GMT 2004
>Closed-Date:    Sun Nov 28 13:51:07 GMT 2004
>Last-Modified:  Sun Nov 28 13:51:07 GMT 2004
>Originator:     Matthias Schuendehuette
>Release:        FreeBSD 5.2-CURRENT
>Organization:
>Environment:
FreeBSD current.best-eng.de 5.2-CURRENT FreeBSD 5.2-CURRENT #8: Sun Jul  4 11:48:54 CEST 2004     root@current.best-eng.de:/raid/obj/usr/src/sys/CURRENT  i386
      
>Description:
Since the commit of sys/kern/vfs_mount.c (1.128) and sys/geom/geom_dev.c (1.76) on 2004-06-17 21:24:13 UTC (phk) vinum is broken in -current. A kernel panic results if vinum is started at boottime or thereafter.
>How-To-Repeat:
Have a working vinum config with "start_vinum=YES" in /etc/rc.conf
Boot a kernel with sources newer than  2004-06-17 21:24:13 UTC
A kernel panic results
>Fix:
      
>Release-Note:
>Audit-Trail:

From: Greg 'groggy' Lehey <grog@FreeBSD.org>
To: Matthias Schuendehuette <msch@snafu.de>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/68698: vinum(4) broken in 5.2-current
Date: Tue, 6 Jul 2004 08:22:54 +0930

 --gatW/ieO32f1wygP
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 On Monday,  5 July 2004 at 14:45:51 +0000, Matthias Schuendehuette wrote:
 >
 >> Number:         68698
 >> Category:       kern
 >> Synopsis:       vinum(4) broken in 5.2-current
 >> Confidential:   no
 >> Severity:       serious
 >> Priority:       medium
 >> Responsible:    freebsd-bugs
 >> State:          open
 >> Quarter:
 >> Keywords:
 >> Date-Required:
 >> Class:          sw-bug
 >> Submitter-Id:   current-users
 >> Arrival-Date:   Mon Jul 05 14:50:20 GMT 2004
 >> Closed-Date:
 >> Last-Modified:
 >> Originator:     Matthias Schuendehuette
 >> Release:        FreeBSD 5.2-CURRENT
 >> Organization:
 >> Environment:
 > FreeBSD current.best-eng.de 5.2-CURRENT FreeBSD 5.2-CURRENT #8: Sun Jul  4 11:48:54 CEST 2004     root@current.best-eng.de:/raid/obj/usr/src/sys/CURRENT  i386
 >
 >> Description:
 > Since the commit of sys/kern/vfs_mount.c (1.128) and sys/geom/geom_dev.c (1.76) on 2004-06-17 21:24:13 UTC (phk) vinum is broken in -current. A kernel panic results if vinum is started at boottime or thereafter.
 >> How-To-Repeat:
 > Have a working vinum config with "start_vinum=YES" in /etc/rc.conf
 > Boot a kernel with sources newer than  2004-06-17 21:24:13 UTC
 > A kernel panic results
 
 Please supply details of the panic.
 
 Greg
 --
 Note: I discard all HTML mail unseen.
 Finger grog@FreeBSD.org for PGP public key.
 See complete headers for address and phone numbers.
 
 --gatW/ieO32f1wygP
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.0 (FreeBSD)
 
 iD8DBQFA6dvGIubykFB6QiMRAmB0AJwNsyanvRL6ZH9kdLt/LK/9CJYfQQCaAvmO
 R9hO8XzQZP4RwT57/thaxfQ=
 =E7Mi
 -----END PGP SIGNATURE-----
 
 --gatW/ieO32f1wygP--

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

 =2D----BEGIN PGP SIGNED MESSAGE-----
 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=
 sk+0x187
 vinum_super_ioctl(c16ebe00,c400464b,c1707000,3,c15269a0) at vinum_super_ioc=
 tl+0x436
 spec_ioctl(cc5a6b80,cc5a6c2c,c05d026d,cc5a6b80,c06e0c45) at spec_ioctl+0x185
 spec_vnoperate(cc5a6b80,c06e0c45,c1506900,28143000,cc5a6b90) at spec_vnoper=
 ate+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
 =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] snafu.de>, Berlin (Germany)
 PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
 =2D----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFA7Exsf1BNcN37Cl8RAqUJAJ9gJ7OqXnmCuwFkPb0KiNjyTDjd8wCdGU7v
 yXve8O7dQoQJfAf7Vw7jcUw=3D
 =3DheX+
 =2D----END PGP SIGNATURE-----

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

 --zaRBsRFn0XYhEU69
 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
 http://www.vinumvm.org/vinum/how-to-debug.html, 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.
 
 Greg
 --
 Note: I discard all HTML mail unseen.
 Finger grog@FreeBSD.org for PGP public key.
 See complete headers for address and phone numbers.
 
 --zaRBsRFn0XYhEU69
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.0 (FreeBSD)
 
 iD8DBQFA7IgWIubykFB6QiMRAj+1AJ9tYcOTsMSmam12HtXV/qXjR87oPQCfQCkY
 rPrsjz9h9mkcWvYzts7NmEo=
 =JlUD
 -----END PGP SIGNATURE-----
 
 --zaRBsRFn0XYhEU69--

From: "Yuriy N. Shkandybin" <jura@networks.ru>
To: <freebsd-gnats-submit@FreeBSD.org>, <msch@snafu.de>
Cc:  
Subject: Re: kern/68698: vinum(4) broken in 5.2-current
Date: Wed, 21 Jul 2004 16:17:39 +0400

 "vinum start" somehow wants already mounted root.
 And want to mention, that mounting / before "vinum start" is workaound.
 For exmple  placing
 start_cmd="mount /;vinum start"  instead  start_cmd="vinum start" in
 /etc/rc.d/vinum
 resolve panics.
 
 Jura
 

From: Jens Schweikhardt <schweikh@schweikhardt.net>
To: GNATS Bug Followup <bug-followup@FreeBSD.org>
Cc:  
Subject: Re: kern/68698: vinum(4) broken in 5.2-current
Date: Sat, 24 Jul 2004 20:15:51 +0200

 I can confirm that setting start_cmd="mount /;vinum start"
 in /etc/rc.d/vinum is a workaround. The panic is gone.
 
 So it appears that "vinum start" has gained the prerequisite of a
 mounted rootfs... Can vinum experts confirm or deny this?
 Could automounting / if it's missing be added to "vinum start"
 or is this the wrong way to fix the issue?
 
 	Jens

From: Matthias Schuendehuette <msch@snafu.de>
To: "Greg 'groggy' Lehey" <grog@FreeBSD.org>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/68698: vinum(4) broken in 5.2-current
Date: Sun, 25 Jul 2004 19:16:51 +0200

 =2D----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 On Thursday 08 July 2004 01:32, Greg 'groggy' Lehey wrote:
 > A ddb stack trace is barely helpful.  As stated at
 > http://www.vinumvm.org/vinum/how-to-debug.html, we really need a
 > dump.
 
 Well, finally here it is:
 
 =2D --------8><------------------------------------------------------------
 GNU gdb 5.3 (FreeBSD)
 Copyright 2002 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you=20
 are
 welcome to change it and/or distribute copies of it under certain=20
 conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for=20
 details.
 This GDB was configured as "i386-portbld-freebsd5.2"...
 panic: unmount: dangling vnode
 panic messages:
 =2D ---
 panic: unmount: dangling vnode
 
 syncing disks, buffers remaining... 208 208 208 208 208 208 208 208 208=20
 208 208 208 208 208 208 208 208 208 208 208=20
 giving up on 176 buffers
 Uptime: 34s
 Dumping 255 MB
  16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
 =2D ---
 #0  doadump () at /usr/src/sys/kern/kern_shutdown.c:236
 
 warning: Source file is more recent than executable.
 
 236		 * (if 'panic' can not dump)
 add symbol table from file "/boot/kernel/vinum.ko" at
 	.text_addr =3D 0xc08817c0
 (kgdb) bt
 #0  doadump () at /usr/src/sys/kern/kern_shutdown.c:236
 #1  0xc055a9ed in boot (howto=3D0x100)=20
 at /usr/src/sys/kern/kern_shutdown.c:381
 #2  0xc055b018 in panic (fmt=3D0xc0726bd6 "unmount: dangling vnode")=20
 at /usr/src/sys/kern/kern_shutdown.c:559
 #3  0xc05b68a0 in vfs_mount_destroy (mp=3D0xc1630800, td=3D0x0)=20
 at /usr/src/sys/kern/vfs_mount.c:534
 #4  0xc05b8935 in getdiskbyname (name=3D0xc1706100 "/dev/da3s1a")=20
 at /usr/src/sys/kern/vfs_mount.c:1502
 #5  0xc088d11e in sdio ()
 #6  0xc088d49b in vinum_bounds_check ()
 #7  0xc088d9d2 in revive_block ()
 #8  0xc088db50 in revive_block ()
 #9  0xc088e567 in initsd ()
 #10 0xc088f316 in vpstate ()
 #11 0xc04f9085 in spec_ioctl (ap=3D0x1)=20
 at /usr/src/sys/fs/specfs/spec_vnops.c:357
 #12 0xc04f8718 in spec_vnoperate (ap=3D0x0)=20
 at /usr/src/sys/fs/specfs/spec_vnops.c:118
 #13 0xc05ca2ed in vn_ioctl (fp=3D0xc17559d4, com=3D0xc400464b,=20
 data=3D0xc16ff800, active_cred=3D0xc14f8d80, td=3D0xc15be000)
     at vnode_if.h:503
 #14 0xc0581997 in ioctl (td=3D0xc15be000, uap=3D0xcc5c4d14) at file.h:258
 #15 0xc06dc040 in syscall (frame=3D
       {tf_fs =3D 0x2f, tf_es =3D 0x2f, tf_ds =3D 0x2f, tf_edi =3D 0x0, tf_e=
 si =3D=20
 0xbfbfe540, tf_ebp =3D 0xbfbfe958, tf_isp =3D 0xcc5c4d74, tf_ebx =3D=20
 0xbfbfe990, tf_edx =3D 0x0, tf_ecx =3D 0x8059c00, tf_eax =3D 0x36, tf_trapn=
 o=20
 =3D 0x16, tf_err =3D 0x2, tf_eip =3D 0x2814f66f, tf_cs =3D 0x1f, tf_eflags =
 =3D=20
 0x246, tf_esp =3D 0xbfbfe52c, tf_ss =3D 0x2f})=20
 at /usr/src/sys/i386/i386/trap.c:1004
 (kgdb) quit
 
 =2D --=20
 Ciao/BSD - Matthias
 
 Matthias Schuendehuette	<msch [at] snafu.de>, Berlin (Germany)
 PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
 =2D----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFBA+sNf1BNcN37Cl8RAoXvAJ912tThXDexm1FWGzbPthfANFFpXQCfUZ2F
 ukWKo7qZ1N+1v2InczFNeIE=3D
 =3DFvwy
 =2D----END PGP SIGNATURE-----
Responsible-Changed-From-To: freebsd-bugs->le 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Sep 9 19:05:35 GMT 2004 
Responsible-Changed-Why:  
Over to volunteer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=68698 

From: Matthias Schuendehuette <msch@snafu.de>
To: freebsd-gnats-submit@freebsd.org
Cc: Lukas Ertl <le@freebsd.org>
Subject: Re: kern/68698: [vinum] vinum(4) broken in 5.2-current
Date: Sat, 27 Nov 2004 18:28:34 +0100

 Works with geom_vinum.ko in the meantime (5.3-STABLE).
 
 PR may be closed. Thanks a lot!
 -- 
 Ciao/BSD - Matthias
 
 Matthias Schuendehuette <msch [at] snafu.de>, Berlin (Germany)
 PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
State-Changed-From-To: open->closed 
State-Changed-By: le 
State-Changed-When: Sun Nov 28 13:50:58 GMT 2004 
State-Changed-Why:  
Closed on submitter's request. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=68698 
>Unformatted:
