|In this Document|
APPLIES TO:Solaris Operating System – Version 11.1 to 11.3 [Release 11.0]
Information in this document applies to any platform.
SYMPTOMSAfter dropping a LUN, you try to destroy a zpool and the following error is seen:
root:~# zpool destroy -f vader
cannot open ‘vader’: pool I/O is currently suspended Running zpool status on the pool returns results similar to the following: root:~# zpool status vader
status: One or more devices are unavailable in response to IO failures.
The pool is suspended.
action: Make sure the affected devices are connected, then run ‘zpool clear’ or
Run ‘zpool status -v’ to see device specific details.
scan: none requested
config: NAME STATE READ WRITE CKSUM
vader SUSPENDED 0 0 0
c0t60xxxxxxxxxxxxxxxxxxxxxxx00A000Fd0 UNAVAIL 0 0 0
root:~# CHANGESA LUN associated with the zpool was dropped prior to attempting to destroy the zpool. CAUSEThe LUN was removed before the pool was destroyed. LUNs must be removed after the pool is destroyed. Otherwise, this issue will occur.
SOLUTIONThe only solution for this issue is to clear the zpool cache, reboot then import the remaining zpools manually. 1. As root, rename /etc/zfs/zpool.cache . mv /etc/zfs/zpool.cache /etc/zfs/zpool.cache.backup
2. Reboot the host.The host may hang on shutdown as it attempts to unmount the filesystems belonging to the suspended zpool. This in turn can sometimes hang since it cannot complete the IO. If this happens, you’ll want to force a reboot from the ILOM/System Controller.
3. When the host boots, list the available pools. zpool importIf the suspended pool is listed, a zpool status should show it as FAULTED. In this case, destroy the pool as normal then go to #4.If the suspended pool is not listed, go to #4.
4. Manually import the listed pools. zpool import <poolName>
5. Start the zones, applications, etc as normal. REFERENCES