HPUX migrating data to a new san

[christian_derek]

Hi,

We are migrating our hpux bl890c from an EVA to a 3par storage system. We bought HPE Services boot from san to simplify our migraiton. The HPE person have created a mirror between VG00 on EVA and a lun presented from the 3par. We just need to ensure we can boot from 3 par and break the mirror after.

Now regarding the data, I was planning to use the same idea to migrate a vg at a time. But, I'm having issue creating the mirror. here are the step I have done

1- present a lun from 3par
2- add the lun in the destination vg
3- mirror the lvol on the newly added disk inside the vg

here is the command an error:
/usr/sbin/lvextend -A y -m 1 /dev/vg_viva_prod/lvol_etc /dev/disk/disk41
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg_viva_prod/lvol_etc" could not be extended.
Failure possibly caused by strict allocation policy

The original disk on the eva is 35 and I'm trying to add it on the disk41 3par.

Thanks,

[Patrick Wallek]

Please post the output of the command:

# vgdisplay -v /dev/vg_viva_prod

abd

# lvdisplay /dev/vg_viva_prod/lvol_etc

[christian_derek]

Hi,

Here you go ...

Thanks,

# vgdisplay -v /dev/vg_viva_prod
--- Volume groups ---
VG Name /dev/vg_viva_prod
VG Write Access read/write
VG Status available
Max LV 2047
Cur LV 6
Open LV 6
Cur Snapshot LV 0
Max PV 2048
Cur PV 2
Act PV 2
Max PE per PV 51200
VGDA 4
PE Size (Mbytes) 1
Unshare unit size (Kbytes) 1024
Total PE 51200
Alloc PE 31764
Current pre-allocated PE 0
Free PE 19436
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 2.2
VG Max Size 50g
VG Max Extents 51200
Cur Snapshot Capacity 0p
Max Snapshot Capacity 50g

--- Logical volumes ---
LV Name /dev/vg_viva_prod/lvol_data
LV Status available/syncd
LV Size (Mbytes) 20480
Current LE 20480
Allocated PE 20480
Used PV 1

LV Name /dev/vg_viva_prod/lvol_var
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 4096
Allocated PE 4096
Used PV 1

LV Name /dev/vg_viva_prod/lvol_opt
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 1024
Allocated PE 1024
Used PV 1

LV Name /dev/vg_viva_prod/lvol_home
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 2048
Allocated PE 2048
Used PV 1

LV Name /dev/vg_viva_prod/lvol_etc
LV Status available/syncd
LV Size (Mbytes) 20
Current LE 20
Allocated PE 20
Used PV 1

LV Name /dev/vg_viva_prod/lvol_fwlog
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 4096
Allocated PE 4096
Used PV 1

--- Physical volumes ---
PV Name /dev/disk/disk35
PV Status available
Total PE 51191
Free PE 19427
Current pre-allocated PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/disk/disk41
PV Status available
Total PE 9
Free PE 9
Current pre-allocated PE 0
Autoswitch On
Proactive Polling On

# lvdisplay /dev/vg_viva_prod/lvol_etc
--- Logical volumes ---
LV Name /dev/vg_viva_prod/lvol_etc
VG Name /dev/vg_viva_prod
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 20
Current LE 20
Allocated PE 20
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation strict
IO Timeout (Seconds) default
Number of Snapshots 0

#

[Patrick Wallek]

Your problem is that your "VG Max Extents" setting is too small to accomodate both your current PV and the new PV.

Your current "VG Max Extents" setting is 51,200.  Your current PV, disk35, consists of 51,191 extents.  As a result LVM is only allowing 9 extents from your new PV, disk41.

Your "PE Size" of 1 MB is VERY SMALL.  Most modern systems I see have a "PE Size" at a minimum of 4 MB, but most are at least 32 MB.

You can try to use 'vgmodify' to modify the maximum size of your VG.

Something like this may work.

Review the change to see if it will work:

# vgmodify -a -r -S 150g /dev/vg_viva_prod

If this doen't complain, then apply the change:

# vgmodify -a -S 150g /dev/vg_viva_prod

Once that is done, check and see if your disk41 is the size that it should be.  If not you may have to do:

# vgmodify -a -E /dev/vg_viva_prod

Once you see the correct size listed in the 'vgdisplay -v' output for disk41, then you should be able to mirror your LVs.

[christian_derek]

Hi,

I tried and here is the error message:

vgmodify -a -r -S 100g /dev/vg_viva_prod
Physical volume "/dev/disk/disk35" requires reconfiguration to be
provisioned to the requested maximum volume group size 102400 MB.
Current number of extents: 51191
Number of extents after reconfiguration: 51189
Physical volume "/dev/disk/disk35" was not changed.

Physical volume "/dev/disk/disk41" requires reconfiguration to be
provisioned to the requested maximum volume group size 102400 MB.
Current number of extents: 9
Number of extents after reconfiguration: 9
Physical volume "/dev/disk/disk41" was not changed.

Thanks,

[Patrick Wallek]

Try adding a '-E' to  your command line and see what happens.

# vgmodify -a -r -E -S 100g /dev/vg_viva_prod

[christian_derek]

still the same

# vgmodify -a -r -E -S 100g /dev/vg_viva_prod
Physical volume "/dev/disk/disk35" requires reconfiguration to be
provisioned to the requested maximum volume group size 102400 MB.
Current number of extents: 51191
Number of extents after reconfiguration: 51189
Physical volume "/dev/disk/disk35" was not changed.

Physical volume "/dev/disk/disk41" requires reconfiguration to be
provisioned to the requested maximum volume group size 102400 MB.
Current number of extents: 9
Number of extents after reconfiguration: 9
Physical volume "/dev/disk/disk41" was not changed.

[Patrick Wallek]

With the way your VG is configured, you may not be able to reconfigure it to allow adding a 2nd PV so you can mirror your file systems.

It appears that you may have to just create a new VG and new LVs and copy your data.

[christian_derek]

Hi,

What is the issue with the VG, is it something I can modify?  HPE was able to do it with vg00

Thanks,

[Patrick Wallek]

Go back and read my response after you posted the 'vgdisplay' output.  The issue is there.

Nutshell version -- Your VG is not configured appropriately to handle the 2nd disk.

If you talked to HPE about VG00 and they did a 'vgmodify' then mention this to them as well. 

[christian_derek]

Hi

OK, in this case I have no other choice than waiting for HPE to call back since copying the data will required a lot more work.

Thanks,