Solaris Volume Manager (SVM) Procedure to Prevent SVM from Overwriting a Disk which is in a ZFS (zpool) Configuration
Last updated on JANUARY 29, 2018
Applies to:Solaris Operating System - Version 10 3/05 to 11.3 [Release 10.0 to 11.0]
Solaris Cluster - Version 3.2 to 4.3 [Release 3.2 to 4.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
When using the Solaris Volume Manager (SVM) 'metainit' command, no checks are done to ensure the disk(s) being added have not been already been allocated to a zfs zpool. This can cause zfs file system corruption.
When a disk in an existing zpool has also been used by Solaris Volume Manager, the zpool may be in a degraded or failed state. The 'zpool status <zpool name> -xv' may show the zpool state similar to the following:
This has resulted in zfs file system corruption.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms