Date: Sun, 12 Apr 2015 23:48:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 199405] Panic trying to mount ZFS pool after 10.1 update Message-ID: <bug-199405-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199405 Bug ID: 199405 Summary: Panic trying to mount ZFS pool after 10.1 update Product: Base System Version: 10.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: drsmithy@gmail.com Created attachment 155528 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155528&action=edit Core dump text file My home FreeBSD servers is panicking trying to mount one of its ZFS pools. It is a VM running on vSphere 5.5 with two LSI SAS9211-8i HBAs presented to it using PCI passthrough and has been quite stable for a couple of years in this configuration. It was recently updated to 10.1 (from 10), but ran successfully for a week or two before the current problem. It was also relatively recently (within the last month or two) updated from 9.3-STABLE. The ZFS pool was not upgraded to the latest features when the system was. Trying to "zpool import -f" on freshly built 10.1 or 9.3 systems causes the same panic. I have also tried importing with readonly=on. I haven't tried systems earlier than 9.3. A second zpool from the same server is working without problems (ie: I was able to mount it on the freshly built 10.1 box with zpool import-f). The text from the panic is: FreeBSD freebsd 10.1-RELEASE-p9 FreeBSD 10.1-RELEASE-p9 #0: Tue Apr 7 01:09:46 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 panic: solaris assert: range_tree_space(rt) == space (0x6b34cb000 == 0x6b3525000), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/space_map.c, line: 130 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: panic: solaris assert: range_tree_space(rt) == space (0x6b34cb000 == 0x6b3525000), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/space_map.c, line: 130 cpuid = 0 KDB: stack backtrace: #0 0xffffffff80963000 at kdb_backtrace+0x60 #1 0xffffffff80928125 at panic+0x155 #2 0xffffffff81b7c22f at assfail3+0x2f #3 0xffffffff81a836e5 at space_map_load+0x3d5 #4 0xffffffff81a69b0e at metaslab_load+0x2e #5 0xffffffff81a6b609 at metaslab_alloc+0x6b9 #6 0xffffffff81aa9ca6 at zio_dva_allocate+0x76 #7 0xffffffff81aa7382 at zio_execute+0x162 #8 0xffffffff80971475 at taskqueue_run_locked+0xe5 #9 0xffffffff80971f08 at taskqueue_thread_loop+0xa8 #10 0xffffffff808f8b6a at fork_exit+0x9a #11 0xffffffff80d0acfe at fork_trampoline+0xe Uptime: 4m26s Dumping 418 out of 8168 MB:..4%..12%..23%..31%..43%..54%..62%..73%..81%..92% I have attached the core.txt file produced, I also have a core dump. This is from trying to import on the fresh 10.1 system. This may be related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193875 ? It would be great if I could even get this pool mounted in a readonly state to pull some of the data off it. Nothing is irreplaceable, but restoring ~9T over the internet takes a long time. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199405-8>