panic: unmount: dangling vnode

Mike B meb at
Sun Aug 15 19:25:16 PDT 2004

Jun Kuriyama wrote:

>After rebooting from previous panic, I had this panic during vinum
>starting.  I can continue booting after removing "vinum_start=YES"
>from /etc/rc.conf.
>Greg, is there what I can help for this?
>panic: unmount: dangling vnode
>cpuid = 0;
>KDB: enter: panic
>[thread 100102]
>Stopped at      kdb_enter+0x2b: nop
>db> trace
>kdb_enter(c0677962) at kdb_enter+0x2b
>panic(c067f68a,c398cc05,e4e7d9e8,c053a62b,c38fa000) at panic+0x131
>vfs_mount_destroy(c38fa000,c3968420) at vfs_mount_destroy+0x1d
>getdiskbyname(c398cc00,e4e7da14,c050abcd,61,c398cc00) at getdiskbyname+0x173
>open_drive(c398cc00,c3968420,0,c07c3247,c398cc00) at open_drive+0x21
>init_drive(c398cc00,0,61,1,c398cc00) at init_drive+0x1c
>read_drive_label(c398cc00,0,e4e7da74,c,61) at read_drive_label+0x11
>check_drive(c393c800,c393c808,408,c07cff26,1) at check_drive+0x4c
>vinum_scandisk(c3938380,c393cc00,c39bf528,c38ed700,e4e7db3c) at vinum_scandisk+0x220
>vinum_super_ioctl(c38ed700,c400464b,c393cc00,c06d8ba0,1) at vinum_super_ioctl+0x4d0
>vinumioctl(c38ed700,c400464b,c393cc00,3,c3968420) at vinumioctl+0x39
>spec_ioctl(e4e7db88,e4e7dc34,c0547b23,e4e7db88,c06ccec0) at spec_ioctl+0x152
>spec_vnoperate(e4e7db88) at spec_vnoperate+0x13
>vn_ioctl(c3975154,c400464b,c393cc00,c3460480,c3968420) at vn_ioctl+0x19f
>ioctl(c3968420,e4e7dd14,3,4,296) at ioctl+0x3e0
>syscall(2f,2f,2f,0,1) at syscall+0x217
>Xint0x80_syscall() at Xint0x80_syscall+0x1f
>--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x28145083, esp = 0xbfbfe52c, ebp = 0xbfbfe958 ---
Standard vinum in -CURRENT is busted. Please check out geom_vinum and 
gvinum in the archives.


More information about the freebsd-current mailing list