Hi,
Is the LUNs being visible to the OS a limitation for me to import a DG to a node? If so what would be the consequenses?
Will this work on this case?
vxdg -fC import diskgroup
Tks,
Joao
Luns need to be accessible at OS level.
You need to be able to see Luns in 'format' output as well as 'vxdisk -o alldgs list'.
... what would be the consequenses?
Attempt to import will fail.
Luns need to be accessible at OS level.
You need to be able to see Luns in 'format' output as well as 'vxdisk -o alldgs list'.
... what would be the consequenses?
Attempt to import will fail.
Hi Joao,
Yes, agree with Marianne, Luns will need to be visible in order to get a successful Diskgroup import.
About doing force import (-fC import), I reckon old versions would still do a force import but this may leave some of your volumes in inconsistent (disabled) state & some volumes may come to work which have the visible disks but the volumes which didn't have Luns will be in disabled state & you should see failed disks in "vxdisk list" output. Though this type of half dg import is not recommended.
This behavior use to happen with 4.x products & infact I recollect this happening with 5.0 as well.
G
Tks. After the LUNs are visible will the disks be visible automatically using the vxdisk?
Note that these LUNs are already part of G in the cluster where this node that cant see LUNs are.
When luns are visable to O/S, you need to use "vxdctl enable" to make there visable to vxdisk.
Mike
