ZFS hangs on 'zfs mount'

[DSTMK]

After updating FreeNAS and upgrading my zpools, I noticed that not all volumes from one of my zpools were available after unlocking the pool. Also, the GUI never completed the unlock action.

I rebooted and tried again for a few times, but without success. The unlock never completed.

I tried to scrub the pool - there were no errors found and the behavior did not change.

So, I decided to investigate. I did a manual "geli attach" for all 8 drives in the pool. Then I did a "zpool import -N" for the pool. Finally, I mounted the volumes one by one. Strangely, there is one volume that causes "zfs mount" to hang indefinitely. There is no action on the HDDs and no IO in "zpool iostat". All other volumes on the same zpool are working just fine. The pool consists of only one raidz2-0 with 8 HDDs


Any advice? I am happy to provide all the information that might be helpful to debug this.

Thanks!

 

[joeschmuck]

Could you be so kind as to list your hardware and which version of FreeNAS you are using?

Also, stop what you are doing unless you are comfortable possibly loosing your data. If I were you I'd roll back to the previous version of FreeNAS and hope your data is intact and then once you post your specs, someone will hopefully help you out.

Good Luck

 

[DSTMK]

Build: FreeNAS-9.3-STABLE-201512121950
Platform: Intel(R) Core(TM) i3-4340 CPU @ 3.60GHz
Memory: 16039MB (ECC)

lspci output:

00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.1 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C226 Series Chipset Family Server Advanced SKU LPC Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
05:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
08:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

​

I just tried to mount the volume read-only and it works! Also, I have a recent backup, so I don't fear loosing my data.

However, I think I am seeing a bug here that should be tracked down and fixed. So here is a clarification:

This thread is not about rescuing my data - it is about improving the quality of FreeNAS/ZFS/FreeBSD.
If a developer wants me to work with him, I am happy to cooperate. If not, I'll just delete the volume and forget about this hickup.

Thanks!

 

[joeschmuck]

I would suggest opening a bug report (use link at top of page) and enter all the data you can to provide the developers the information required in order to look at the problem. If you are willing to test on your system, point that out because they may desire you to grab some extra data.

 

[DSTMK]

Done - see https://bugs.freenas.org/issues/12830