Bug 193965 - [zfs] zpool coredump on import
Summary: [zfs] zpool coredump on import
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.2-STABLE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-27 06:06 UTC by will
Modified: 2015-11-15 16:41 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description will 2014-09-27 06:06:32 UTC
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.
Comment 1 will 2014-09-29 05:37:09 UTC
It's worth noting that even after getting the pool imported on mfsbsd, adding the new drive and resilvering, thens shuttind down gracefully, my 10.0-STABLE OS on the zpool itself still fails to import.
Comment 2 will 2014-10-08 00:55:20 UTC
My kernel panics on boot were resolved after re-adding the cache and logging devices. Does this mean that it's not safe to remove a log device on ZFS on root?
Comment 3 Steven Hartland freebsd_committer 2015-03-15 11:59:53 UTC
Please try with stable/10 and if still unsuccessfully current to see if this is already fixed as 10.0-RELEASE is pretty old now.
Comment 4 will 2015-11-15 16:41:02 UTC
Hey,

I know this is a fairly old bug, but I was able to reproduce it on 10.2-STABLE by removing the log device and rebooting. I'll try and produce some more dumps or a patch today.