Solaris Cluster: Changes to Veritas Disk Group Configuration Triggers HAStoragePlus Restarts
(Doc ID 2169433.1)
Last updated on AUGUST 19, 2016
Applies to:Solaris Cluster - Version 3.3 to OSC 3.3 3/13 [Release 3.3]
Solaris Cluster Geographic Edition - Version 3.3 to OSC 3.3 3/13 [Release 3.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
An HAStoragePlus and all dependent resource get restarted soon after changes done to the Veritas Volume Manager diskgroup managed by the HAStoragePlus resource
The messages shows errors like
SC[,SUNW.HAStoragePlus:10,RG-NAME,HASTORAGEPLUS-RS-NAME,hastorageplus_probe]: Failed to open device /dev/vx/rdsk/DISKGROUP-NAME/VOLUME-NAME - No such device or address
SC[,SUNW.HAStoragePlus:10,RG-NAME,HASTORAGEPLUS-RS-NAME,hastorageplus_probe]: Issuing a resource restart request because of probe failures.
The customer created a new volume while the hastorageplus was active, with fault monitor enabled and without immediate execution of cldg sync.
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