Solaris Cluster 3.x Syncing a VxVM Diskgroup may Affect Another VxVM Diskgroup
(Doc ID 1011140.1)
Last updated on AUGUST 05, 2021
Applies to:Solaris Cluster - Version 3.0 to 3.3 U2 [Release 3.0 to 3.3]
Solaris Cluster Geographic Edition - Version 3.1 to 3.3 U2 [Release 3.1 to 3.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
This document describe the interactions between VxVM diskgroup and Solaris Cluster device service. It should provide a clear picture how the VxVM disk group will be synced with the device tree and the cluster CCR (Cluster Configuration Repository).
Let's assume you have two diskgroups datadg and oradg.
You have made some changes to oradg (e.g. created a new volume, or changed permissions of volume) and then run
SC 3.x: # scconf -c -D name=oradg,sync
SC 3.2 and above: # cldg sync oradg
The changes of the diskgroup oradg are now in sync with the cluster CCR
But if you do changes to another disk group in this example datadg before doing the 'cldg sync oradg' the following issues can occur:
If you have previously renamed /dev/vx/dsk/datadg/vol to /dev/vx/dsk/datadg/vol2 via "vxedit rename" and you have NOT run "cldg sync datadg" but you now run "cldg sync oradg", then the following is observed in /var/adm/messages:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!