Zpool import can fail when a zpool exists on the VTOC s2 slice
(Doc ID 1963384.1)
Last updated on MAY 08, 2023
Applies to:
Solaris Operating System - Version 10 6/06 U2 and laterInformation in this document applies to any platform.
Symptoms
The zpool import command can fail if a vdev device path is different from the previous device path and the previous one is not the cxtxdxsx format. 3rd-party multi-path softwares (EMC PowerPath, HITACH HDLM, Veritas VxDMP, etc.) are often involved as they use non-cxtxdxsx formats to represent device paths.
In the following example, the zpool was imported with /dev/dsk/ecmpower17c. The device is now c5t60000970000495700053533031373633d0.
When reading zfs vdev labels from the s6 slice, LABEL 0 and 1 are unreadable though LABEL 2 and LABEL 3 are fine.
Cause
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
| Symptoms |
| Cause |
| Solution |