Date: Sat, 27 Sep 2014 06:06:32 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193965] New: [zfs] zpool coredump on import Message-ID: <bug-193965-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193965 Bug ID: 193965 Summary: [zfs] zpool coredump on import Product: Base System Version: 10.0-RELEASE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: will@worrbase.com I had a pool with 3 mirrors, a single floating disk in a RAID-0 and an SSD that was both a cache and a log device. I got a new drive, and wanted to mirror the single disk (bringing me up to four mirrors) and remove the SSD. I booted normally and did a zpool remove tank gpt/log and zpool remove tank gpt/cache. I powered off to install the hard disk. I booted with the new disk attached and the SSD detached, and the machine kernel panicked. I removed the disk and reattached the SSD as normal, and the machine panicked again. I removed both the new disk and the SSD, and the machine still panicked. I booted into mfsbsd (10, still). I did a zpool import -R /a tank (after a mkdir /a, of course). This caused a coredump in zpool (see https://imgur.com/25yAdon). The coredump is available here: http://kefka.worrbase.com/zpool.core Finally, I did a zpool import -F -n -R /a tank, and the pool imported successfully. -- 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-193965-8>