This is a discussion on VM 4.1 - changes to default rootdg - Veritas Volume Manager ; Did the way rootdg is handled change with Volume Manager 4.1? I have a Solaris 9 box with VM 3.5, it's root disks are under DiskSuite/SVM (evil competitor) control. "vxdisk" list shows them with a status or "error". I know ...
Did the way rootdg is handled change with Volume Manager 4.1?
I have a Solaris 9 box with VM 3.5, it's root disks are under DiskSuite/SVM
(evil competitor) control. "vxdisk" list shows them with a status or "error".
I know that error means " they are not under VM contol".
I have a Solaris 10 box with VM 4.1, it's root disks are under DiskSuite/SVM
(evil competitor) control. "vxdisk list" shows them with a status or "online
invalid".
What is the difference between the two status'?
I believe there's some change in how 4.1 handles a default rootdg disk group?
I expected to see, through VEA, the Solaris 10 systems root disks under
a rootdg since I specified that in the installation of VM 4.1.
Thank you