>Number: 172092 >Category: kern >Synopsis: zfs import panics kernel >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Sep 26 12:50:15 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Oliver Adler >Release: 9.0-RELEASE-p3 >Organization: N/A >Environment: FreeBSD i5.a999.de 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Using a 2.5" external USB 3.0 disk with 750 GB. On the disk is a bootable 9.0 FBSD. The disk was used as boot disk on a i386 atom system. Then using it on a amd64 system with zpool import -o altroot=/mnt -f zroot orked fine. After shutting down the system with shutdown -p now the disk can no more be used.
Issuing zpool list or zpool import -o altroot=/mnt -f zroot on the amd64 system panics the kernel. Also attaching the device to the i386 system panics the atom system. The failed assertion is in the file ddt.c line 129. I have a picture of the panic. My assumption is, that there is a problem with deduplication (because on the disk is one dataset with switched on dedup). The data of the disk is no more accessible. >How-To-Repeat: Using this disk, plugging it to either the amd64 or the i386 system Issuing zpool list and the panic shows up If you have any patches to test I will do this. I will keep the disk in this state for some time. If I can help in any way, please ask me. >Fix: >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
