Quote:
Originally Posted by
Voran
It seem not assigned to any vg
Yes: it is not assigned to a VG
in this system. The information about which disk belongs to which volume group is stored on the disk (the LVCB, etc.) but maintained in the ODM. Operations like
importvg read the information stored on the disk to (re-)build the ODM information.
synclvodm try to solve conflicts in the case of these two data sets becoming unsynchronized.
Do an
importvg without the "-L" (learning) option. naming conflicts will be automatically resolved. You can tell from a PVID being shown in the output of
lspv that the disk has to have been part of a VG already. This PVID is also stored on the disk and - by importing the VG - copied into the ODM.
Quote:
but if I tried to assigned hdisk1 to rootvg
Be glad that this won't work: by assigning a PV to a VG the volume is reformatted. This - if successful - would have erased all the data you wanted to import.
A further hint: after importing the VG check
/etc/filesystems. Mount points are part of the FS properties and accordingly this file (which is also a representation of ODM information) is updated. Still, you probably might not want the mount points automatically assigned by the system to resolve the conflicts. Therefore, before the
mount -a do override the mount points there.
I hope this helps.
bakunin