So what I understand overall is, I assign this new lun to all cluster nodes , remove the orignal lun from all cluster nodes and since the lun has lvm and I don't need the original lun , I don't need to worry about vgiimport(changing the vg name) . right?
Thanks
Paras.
On Thu, Nov 21, 2013 at 12:23 PM, Bryn M. Reeves <bmr@xxxxxxxxxx> wrote:
On 11/21/2013 06:03 PM, Paras pradhan wrote:The main use for vgimportclone is to allow the original and replicated
> Thanks. So after vgimportclone , I can mount my new lun it seems (?).
LUNs to co-exist on the system. This didn't seem to be your original
intent so you should read the man page for the command carefully and
decide if it's appropriate for the configuration you want to implement.
If you're removing the original LUN there's no reason to use
vgimportclone but as Bob said earlier you need to do this on all nodes
of the cluster before you try to mount anything.
No - one of the arguments to vgimportclone is a new name for the VG.
> What if I remove the original lun (undefine from SAN) from the node so
> that only the new lun is seen from the os? If I do that I don't even
> need to vgiimport and I can mount the lun with the same vgname? Am i
> correct?
Check the documentation and make sure this is what you want to do.
Regards,
Bryn.
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
