Date: Wed, 18 Feb 2009 14:51:50 +0800 From: Ganbold <ganbold@micom.mng.net> To: Cy Schubert <Cy.Schubert@komquats.com> Cc: freebsd-stable@freebsd.org Subject: Re: ZFS Panic Message-ID: <499BB006.8040105@micom.mng.net> In-Reply-To: <200902180543.n1I5hVDF072033@cwsys.cwsent.com> References: <200902180543.n1I5hVDF072033@cwsys.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Cy Schubert wrote: > I got this panic after issuing reboot(8). > > FreeBSD 7.1-STABLE FreeBSD 7.1-STABLE #0: Tue Feb 17 19:29:23 PST 2009 > cy@cwsys:/export/obj/export/home/cy/test/test-stable7/sys/DEBUG i386 > > > FreeBSD/i386 (bob) (ttyd0) > > login: Feb 17 21:22:56 bob reboot: rebooted by root > Feb 17 21:22:56 bob syslogd: exiting on signal 15 > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...2 2 2 2 1 1 1 1 0 0 0 0 0 0 done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > All buffers synced. > panic: insmntque() failed: error 16 > cpuid = 0 > KDB: enter: panic > [thread pid 1086 tid 100090 ] > Stopped at kdb_enter_why+0x3a: movl $0,kdb_why > db> bt > Tracing pid 1086 tid 100090 td 0xc2bfd230 > kdb_enter_why(c087ef4a,c087ef4a,c2b1b5b4,ebf8da58,0,...) at > kdb_enter_why+0x3a > panic(c2b1b5b4,10,c2b24a40,ebf8da64,c38e6000,...) at panic+0x136 > gfs_file_create(84,c346d8a0,c342d5a0,c2b24a40,c346d8a0,...) at > gfs_file_create+0x86 > gfs_dir_create(84,c346d8a0,c342d5a0,c2b24a40,0,...) at gfs_dir_create+0x2c > zfsctl_mknode_snapdir(c346d8a0,c2b1b54f,275,25d,c3419520,...) at > zfsctl_mknode_snapdir+0x53 > gfs_dir_lookup(c346d8a0,c2b21126,ebf8db74,c091521c,ebf8db38,...) at > gfs_dir_lookup+0xd1 > zfsctl_root_lookup(c346d8a0,c2b21126,ebf8db74,0,0,...) at > zfsctl_root_lookup+0xdc > zfsctl_umount_snapshots(c342d5a0,80000,c3acb800,c3216844,0,...) at > zfsctl_umount_snapshots+0x4e > zfs_umount(c342d5a0,80000,c2bfd230,c2bfd230,c088a687,...) at zfs_umount+0x53 > dounmount(c342d5a0,80000,c2bfd230,e26988ac,0,...) at dounmount+0x430 > vfs_unmountall(c087ed87,0,c087edeb,128,0,...) at vfs_unmountall+0x4e > boot(c090b5d0,0,c087edeb,ab,ebf8dd2c,...) at boot+0x44f > reboot(c2bfd230,ebf8dcfc,4,c0885aef,c08c38a8,...) at reboot+0x4b > syscall(ebf8dd38) at syscall+0x2b3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (55, FreeBSD ELF32, reboot), eip = 0x280bc947, esp = > 0xbfbfeb7c, ebp = 0xbfbfebb8 --- > db> > > Forceably unmounting ZFS filesystems prior to issuing reboot(8) mitigates > the panic. > I have experienced ZFS related panic with RELEN_7 in November last year and got a fix from kib@. But I'm not quite sure whether yours and mine are the same case, but might help following patch (for /usr/src/sys/cddl/compat/opensolaris/kern/opensolaris_kobj.c and /usr/src/sys/cddl/compat/opensolaris/sys/vnode.h): http://lists.freebsd.org/pipermail/freebsd-stable/2008-November/046752.html Ganbold > > -- I was the best I ever had. -- Woody Allen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?499BB006.8040105>