zfs(1M) and zpool(1M) Commands Hang on a Suspended ZFS Pool
(Doc ID 1457074.1)
Last updated on APRIL 02, 2021
Applies to:Solaris Operating System - Version 10 11/06 U3 to 10 9/10 U9 [Release 10.0]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
***Checked for relevance on 22-Dec-2015***
A ZFS Pool will become suspended due to IO errors that faults the vdevs to the point where there are insufficient replicas and the zpool can no longer service IO requests; eg: a single vdev pool encounters a vdev failure, more than two vdevs within a RAIDZ1 fail, or both sides of a mirror fail. failmode=wait is the default action. Refer to the zpool(1M) man page for other options.
Commands such as zfs(1M) and zpool(1M) will hang even if the commands are not associated with the zpool that is suspended. A panic or reboot is the only way to clear the hang. If possible, gather a system crash dump from the reboot to match with cause by using "reboot -d" or issuing a break sequence and typing "sync" and the OK prompt (SPARC Only). Refer to the System Administration documentation for the server or the following document:
How to Force a Crash Dump When the Solaris Operating System is Hung <Document 1004506.1>
This is triggered when a zpool has become suspended due to IO errors that faults the vdevs to the point where there are insufficient replicas and the zpool can no service IO requests.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Oracle Solaris ZFS Resource Center|