Add new disks to VG owned by SG

[Fuad_1]

Hi,

I want to add new disks inot VG owned by SG, without halting package. I used SAM to add new disks, but I got message that I have to undistribute VG.

Thanks.

[Alex Lavrov.]

Do you create news filesystems there or just add disks?

Alex.

[Pedro Cirne]

Hi,

Is this a SG with VG in shared mode? If it is, you can't do it on-line.

After adding the disk to VG you must vgexport to the other node and then vgimport the VG information. You may check man pages on how to do it, don't forget the "-p" flag, otherwise the VG information will be erased from LVM tab.

Enjoy :)

Pedro

[Fuad_1]

Hi,

In this stage, I need to add disks to VG owned by package.

Thanks.

[mirco_1]

hi,

the step in summary is:
{if vg is already in the cluster}

NODE A :
# pvcreate /dev/rdsk/cXtYdY

# vgextend /dev/dsk/cXtYdZ
# vgextend
# vgexport -v -p -s -m

[Alex Lavrov. · Accepted solution]

If you only add disks to VG, the map file stay the same, since there is only VGID and map of the lvols.

Alex.

[Fuad_1]

Hi micro,

I pvcreate one disk, then I vgextend it which was successfull, and same for the second disk. Then I pvcreate all remaining disks, and alt disks for all remaining including first two disks. Now, I start vgextend the third disk but it gives me error vgcfgbackup: Invalid LVMREC on first disk.

Thanks.

[Fuad_1]

Alex,

You point is valid. The new disks are sucessfully created in VG that already exist in primary node. I did not create any new LV's, but I want to update lvmtab on the secondary node. I use vgexport -v -p -s -m, then message says vg still active. One the secondary node, vgimport -v -s -m , which says vg already exists.

Thanks.

[Alex Lavrov.]

You used "-p" option, so no changes were made to the VG and it tells you that it's still active just for the information. It's ok.

On the other node, you have to remove the vg.
vgexport vgXX

Thean recreate the dir and group file:
mkdir /dev/vgXX
mknod /dev/vgXX/group c 64 0xXX0000

Then you perform "vgimport".

Alex.

[Fuad_1]

Hi,

vgimport does not work properly, as the disks appended in secondary lvmtab file are less than the primary one. Also, I have the disks start with C16 and alt disks start with C20 in primary, but in secondary they starts with C20!!!

[Alex Lavrov.]

Hey,
I don't think I understood the problem ... What do you mean by "less"?

Alex.

[Fuad_1]

I have added 10 new disks, with alt. disks, total 20. This is OK in primary node, but I have found 17 disks in secondary all start with C20 as alt. disks. This happen after I vgexport VG from sec., and then re-import and export VG.