Quote:
Originally Posted by
filosophizer
[...]As you can see the it says the VOLUME GROUP is in concurrent mode and when I go and list a concurrent VGs
there is nothing
cl_extendlv: VG pb0oravg is concurrent[...]
I think the error message is misleading. Your Big VG is not concurrent. However, the cluster seems to have a problem in recognising/handling it correctly. From HACMP 5.1 on the default type of VG for shared VG is Enhanced Concurrent Mode so I'd suggest you start with converting your old-style VG to such an ECM VG.
Stop HACMP cluster.
Varyon the VG manually on node1
# chvg -C <yourvg>
Varyoff the VG manually on node1
Varyon the VG manually on node2
# chvg -C <yourvg>
Verify and synchronise the cluster with the autorepair function enabled!
# smitty hacmp
-> Extended Configuration
-> Extended Verification and Synchronization
After a successful synchronisation start over.