Solaris Volume Manager (SVM) metadb May Show Location for Solaris Cluster device id "DID" Without Slice 7 or Slice 6 (Doc ID 2064479.1)

Last updated on APRIL 19, 2017

Applies to:

Solaris Cluster - Version OSC 3.3 3/13 and later
Sun Solaris Volume Manager (SVM) - Version 11.10.0 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

When Solaris Volume Manager (SVM) metasets used in Solaris Cluster we add the disks to the metaset specifying their cluster device id also known as "DID". The metaset utility will change the partitioning of devices that are added to it. A small part  of each drive is reserved for SVM metadb (meta database) in slice 7 on SMI labeled disks and slice 6 on EFI disks.  The remainder of the space on each drive is placed into slice 0. After the disk has been successfully added metadb utility normally shows metadb location on /dev/did/dsk/d<number>s7 or /dev/did/dsk/d<number>s6 on EFI labeled disk. However in some cases you may see that metadb location is shown on /dev/did/dsk/d<number> (no silce)

For example:

 

Cause

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