topic Re: lvextend in Operating System - HP-UX

lvextend

Deborah Weatherspoon — Mon, 10 Sep 2007 08:04:24 GMT

Hi all,

I tried to add a new disk and then try to extend it to 70G, however it did not increase when I umounted and mounted it. Did it actually work ? If not, can it be fixed ?

adm3:[/] # pvcreate -f /dev/rdsk/c10t1d5
Physical volume "/dev/rdsk/c10t1d5" has been successfully created.
adm3:[/] # vgextend /dev/vg03 /dev/dsk/c10t1d5
vgextend: Warning: Max_PE_per_PV for the volume group (12799) too small for this PV (30719).
Using only 12799 PEs from this physical volume.
Current path "/dev/dsk/c10t0d3" is an alternate link, skip.
Volume group "/dev/vg03" has been successfully extended.
Volume Group configuration for /dev/vg03 has been saved in /etc/lvmconf/vg03.conf
adm3:[/] # lvextend -L 71680 /dev/vg03/lvol1
Logical volume "/dev/vg03/lvol1" has been successfully extended.
Volume Group configuration for /dev/vg03 has been saved in /etc/lvmconf/vg03.con

--- Volume groups ---
VG Name /dev/vg03
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 12799
VGDA 4
PE Size (Mbytes) 4
Total PE 25596
Alloc PE 17920
Free PE 7676
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg03/lvol1
LV Status available/syncd
LV Size (Mbytes) 71680
Current LE 17920
Allocated PE 17920
Used PV 2

--- Physical volumes ---
PV Name /dev/dsk/c8t0d3
PV Name /dev/dsk/c10t0d3 Alternate Link
PV Status available
Total PE 12797
Free PE 0
Autoswitch On

PV Name /dev/dsk/c10t1d5
PV Status available
Total PE 12799
Free PE 7676
Autoswitch On

adm3:[/] #

Re: lvextend

Ludovic Derlyn — Mon, 10 Sep 2007 08:10:03 GMT

hi,

Your problem is due to your VG
Vg03 has been created with a disk of 50g, (max PE par Pv * PE size so 12799* *4) and you should add a disk of 70G
Only size of 50G will be set

Two solutions:

- destruct and create a new vg (save data before and restore after)

- Add disk of 50 G only

regards
L-DERLYN

Re: lvextend

Patrick Wallek — Mon, 10 Sep 2007 08:14:02 GMT

You missed a step. You extended the LV, but you never extended the filesystem that is on the LV. Until you do that bdf will still show the old size.

You need to do 1 of 2 things:

1) IF YOU HAVE ONLINE JFS -- fsadm -b 71680m /dev/vg03/lvol1
or
(assuming /dir is where this LV is mounted)
fsadm -b 71680m /dir

2) If you DO NOT have online JFS --
umount /dir
extendfs /dev/vg03/rlvol1
mount /dir

Re: lvextend

Robert-Jan Goossens — Mon, 10 Sep 2007 08:17:01 GMT

Hi Deborah,

You forgot to extend the filesystem. use fsadm or extendfs (depends if you have OnlineJFS installed to extend the filesystem.

--
vgextend: Warning: Max_PE_per_PV for the volume group (12799) too small for this PV (30719).
--

Your current volume group configuration will not allow you to use the full capacity of your disk new lun/disk.
Max_Pe_Per_PV (12799) * PE Size (Mbytes) 4 = +/- 50 GB

Your disk is 30719 * 4 MB = +/- 120 GB

Regards,
Robert-Jan

Re: lvextend

James R. Ferguson — Mon, 10 Sep 2007 08:18:49 GMT

Hi:

Well, you added only 12,799 4MB physical extents to your volume group, although you could not use all of physical extents that the physical disk had to offer. This constriant is a function of the paramters used during the original 'vgcreate'.

Next, you successfully extended the logical volume by 71680/4 or 17920 extents as shown in your 'vgdisplay'.

As yet you have NOT extended the filesystem contained *within* the logical volume --- or at least you haven't stated or shown that.
Until you do that, a 'bdf' or 'df' will not show any change in the mounted filesystem space. Use 'fsadm' or 'extendfs' to enlarge your filesystem.

Regards!

...JRF...

Re: lvextend

Pete Randall — Mon, 10 Sep 2007 08:19:43 GMT

Here is the problem:

"vgextend: Warning: Max_PE_per_PV for the volume group (12799) too small for this PV (30719)."

When the VG was originally created, max_pe was allowed to default and therefor was set to accomodate the original physical volume. This new, larger volume exceeds that size so only part of it is gets used.

Your solution is either to delete and re-create the VG with a large max_pe or to make this new disk into a separate VG.

Pete

Re: lvextend

Torsten. — Mon, 10 Sep 2007 08:45:32 GMT

What is your OS version?
In case of 11.23 or 11.31 you can adjust the maximum values via vgmodify. This tool comes per patch in 11.23.

Re: lvextend

Deborah Weatherspoon — Mon, 10 Sep 2007 09:35:10 GMT

Thanks all,

It appears to be ok....

# vgdisplay -v vg03
--- Volume groups ---
VG Name /dev/vg03
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 12799
VGDA 4
PE Size (Mbytes) 4
Total PE 25596
Alloc PE 17920
Free PE 7676
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg03/lvol1
LV Status available/syncd
LV Size (Mbytes) 71680
Current LE 17920
Allocated PE 17920
Used PV 2

--- Physical volumes ---
PV Name /dev/dsk/c8t0d3
PV Name /dev/dsk/c10t0d3 Alternate Link
PV Status available
Total PE 12797
Free PE 0
Autoswitch On

PV Name /dev/dsk/c10t1d5
PV Status available
Total PE 12799
Free PE 7676
Autoswitch On

adm3:[/] #

/dev/vg03/lvol1 73400320 52367808 20876824 71% /u03

Re: lvextend

Torsten. — Mon, 10 Sep 2007 09:39:01 GMT

You should add the alternate link for PV Name /dev/dsk/c10t1d5 too!

Re: lvextend

Deborah Weatherspoon — Mon, 10 Sep 2007 10:26:32 GMT

Thanks Torsten,

This is a first for me, could you provide the command.

Re: lvextend

Sp4admin — Mon, 10 Sep 2007 10:29:21 GMT

If you have Online-JFS you can extend it on the fly. If not you will need to umount the filesystem and then extend it using extendfs and then mount the filesystem.

sp,

Re: lvextend

Torsten. — Mon, 10 Sep 2007 10:29:53 GMT

According to the output above

PV Name /dev/dsk/c8t0d3
PV Name /dev/dsk/c10t0d3 Alternate Link
...
PV Name /dev/dsk/c10t1d5

it *could* be c8t1d5.
Anyway, you should run
vgscan -p -v
to check this.

Let's assume we have the correct device, run

vgextend /dev/vg03 /dev/dsk/c8t1d5
and check with vgdisplay.

You should have an "alternate link" entry now.

Re: lvextend

Deborah Weatherspoon — Mon, 10 Sep 2007 11:07:10 GMT

I'm getting an error message.

vgextend /dev/vg03 /dev/dsk/c10t1d5
vgextend: Warning: Max_PE_per_PV for the volume group (12799) too small for this PV (30719).
Using only 12799 PEs from this physical volume.
Current path "/dev/dsk/c10t0d3" is an alternate link, skip.
vgextend: The physical volume "/dev/dsk/c10t1d5" is already recorded in the "/etc/lvmtab" file.

Re: lvextend

Torsten. — Mon, 10 Sep 2007 11:11:00 GMT

vgextend /dev/vg03 /dev/dsk/c10t1d5
vgextend: Warning: Max_PE_per_PV for the volume group (12799) too small for this PV (30719).
Using only 12799 PEs from this physical volume.

See earlier posts - this space cannot be used currently.

vgextend: The physical volume "/dev/dsk/c10t1d5" is already recorded in the "/etc/lvmtab" file.

Yes it is. There must be another device file for this volume. How about the vgscan -p -v output?

Re: lvextend

Deborah Weatherspoon — Mon, 10 Sep 2007 11:22:24 GMT

/dev/vg03
/dev/dsk/c8t0d3
/dev/dsk/c8t1d5
/dev/dsk/c10t0d3
/dev/dsk/c10t1d5

Re: lvextend

Torsten. — Mon, 10 Sep 2007 11:29:02 GMT

Now run
vgextend /dev/vg03 /dev/dsk/c8t1d5
and check with vgdisplay -v vg03

Re: lvextend

Deborah Weatherspoon — Mon, 10 Sep 2007 11:36:58 GMT

Same error message.

# vgextend /dev/vg03 /dev/dsk/c8t1d5
vgextend: Warning: Max_PE_per_PV for the volume group (12799) too small for this PV (30719).
Using only 12799 PEs from this physical volume.
Current path "/dev/dsk/c10t0d3" is an alternate link, skip.
vgextend: The physical volume "/dev/dsk/c8t1d5" is already recorded in the "/etc/lvmtab" file.
adm3:[/u03/oradata/MIGR] # vgdisplay -v vg03
--- Volume groups ---
VG Name /dev/vg03
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 12799
VGDA 4
PE Size (Mbytes) 4
Total PE 25596
Alloc PE 17920
Free PE 7676
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg03/lvol1
LV Status available/syncd
LV Size (Mbytes) 71680
Current LE 17920
Allocated PE 17920
Used PV 2

--- Physical volumes ---
PV Name /dev/dsk/c8t0d3
PV Name /dev/dsk/c10t0d3 Alternate Link
PV Status available
Total PE 12797
Free PE 0
Autoswitch On

PV Name /dev/dsk/c10t1d5
PV Status available
Total PE 12799
Free PE 7676
Autoswitch On

adm3:[/u03/oradata/MIGR] #

Re: lvextend

Torsten. — Mon, 10 Sep 2007 11:44:04 GMT

Please post
uname -a
strings /etc/lvmtab

Re: lvextend

TwoProc — Mon, 10 Sep 2007 11:48:11 GMT

See Pete Randalls' previous posting.

You've exceeded the maximum amount of PE's a volume group can have. You need to backup the drives contained volume group, drop the volume group, and recreate the volume using the "-e" switch.

From your display above you'll notice two things:
a) Max PE per PV 12799
and for each PV..

--- Physical volumes ---
PV Name /dev/dsk/c8t0d3
...
Total PE 12797

PV Name /dev/dsk/c10t1d5
...
Total PE 12799

So, notice on c8t0d3 - you're 2 PE's away from the max (only 8M left to allocate), and on c10t1d5, you're already maxed out.

Only thing left to do is backup, recreate using the "-e" switch, create your sizes as you need, then restore.

Re: lvextend

Deborah Weatherspoon — Mon, 10 Sep 2007 12:20:55 GMT

adm3:[/] # uname -a
HP-UX adm3 B.11.11 U 9000/800 124464646 unlimited-user license
adm3:[/] # strings /etc/lvmtab
/dev/vg00
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/vg01
/dev/dsk/c8t0d1
/dev/dsk/c10t0d1
/dev/vg02
/dev/dsk/c8t0d2
/dev/dsk/c10t0d2
/dev/vg03
/dev/dsk/c8t0d3
/dev/dsk/c10t0d3
/dev/dsk/c10t1d5
/dev/vg05
/dev/dsk/c8t1d4
/dev/dsk/c10t1d4
/dev/vg06
/dev/dsk/c8t0d7
/dev/dsk/c10t0d7
/dev/vg07
/dev/dsk/c8t1d0
/dev/dsk/c10t1d0
/dev/vg08
/dev/dsk/c8t1d2
/dev/dsk/c10t1d2
/dev/vg09
/dev/dsk/c8t1d5
adm3:[/] #