topic Re: Cannot extend filesystem in Operating System - HP-UX

Cannot extend filesystem

WSS — Fri, 16 Nov 2007 06:58:37 GMT

Hi All,

I can't extend a logical volume by 1gb, even though there's 5gb free, see below -

root@ugos388# lvextend -L 1264 /dev/vgclwss/lvmp07
lvextend: Not enough free physical extents available.
Logical volume "/dev/vgclwss/lvmp07" could not be extended.
root@ugos388# vgdisplay vgclwss | grep Size
PE Size (Mbytes) 16
root@ugos388# vgdisplay vgclwss | grep Free
Free PE 315
root@ugos388#

Am not getting the usual strict allocation policy error... Just not enough extents.

The volume group is a HA VG and part of a service guard package...

HPUX 11i V23 - RX4640 Itanium server.

Any ideas??

Thanks in advance.
Trev

Re: Cannot extend filesystem

Duncan Edmonstone — Fri, 16 Nov 2007 07:14:29 GMT

Hi Trev,

bet that's a busy old system at the moment eh? ;o)

Can you post the output of

lvdisplay /dev/vgclwss/lvmp07

and

vgdisplay /dev/vgclwss

HTH

Duncan

Re: Cannot extend filesystem

Jdamian — Fri, 16 Nov 2007 07:16:41 GMT

Check if the LV is mirrored and/or PVG-distributed.

Re: Cannot extend filesystem

WSS — Fri, 16 Nov 2007 07:22:19 GMT

Why hello Duncan, how are you?
Good to hear from you... Yes, things been busy of late :-) As you can imagine!!

Ok output is as follows -

root@ugos388# vgdisplay vgclwss
--- Volume groups ---
VG Name /dev/vgclwss
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 9
Act PV 9
Max PE per PV 65535
VGDA 18
PE Size (Mbytes) 16
Total PE 29115
Alloc PE 28800
Free PE 315
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

root@ugos388# lvdisplay /dev/vgclwss/lvmp07
--- Logical volumes ---

LV Name /dev/vgclwss/lvmp07
VG Name /dev/vgclwss
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 10240
Current LE 640
Allocated PE 640
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation PVG-strict/distributed
IO Timeout (Seconds) default

Any ideas?

Does it have something to do with the 'Exclusive' VG Status??

Thanks alot
Trev

Re: Cannot extend filesystem

Duncan Edmonstone — Fri, 16 Nov 2007 07:25:10 GMT

Trev,

No it probably has to do with the PVG strict allocation status.

probably some PVs in the VG are full while others are not - PVG strict allocation wants to put each extent on a seperate LUN.

vgdisplay -v vgclwss

will tell us more

HTH

Duncan

Re: Cannot extend filesystem

WSS — Fri, 16 Nov 2007 07:38:33 GMT

root@ugos388# vgdisplay -v vgclwss
--- Volume groups ---
VG Name /dev/vgclwss
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 9
Act PV 9
Max PE per PV 65535
VGDA 18
PE Size (Mbytes) 16
Total PE 29115
Alloc PE 28800
Free PE 315
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LVName /dev/vgclwss/lvmp01
LV Status available/syncd LV Size (Mbytes) 22528
Current LE 1408
Allocated PE 1408
Used PV 4

LVName /dev/vgclwss/lvmp02
LV Status available/syncd
LV Size (Mbytes) 22528
Current LE 1408
Allocated PE 1408
Used PV 4

LVName /dev/vgclwss/lvmp03
LV Status available/syncd LV Size (Mbytes) 22528
Current LE 1408 Allocated PE 1408
Used PV 4

LVName /dev/vgclwss/lvmp04
LV Status available/syncd
LV Size (Mbytes) 22528
Current LE 1408
Allocated PE 1408
Used PV 4

LVName /dev/vgclwss/lvmp05
LV Status available/syncd
LV Size (Mbytes) 22528
Current LE 1408
Allocated PE 1408
Used PV 4

LVName /dev/vgclwss/lvmp06
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 640
Allocated PE 640
Used PV 4

LVName /dev/vgclwss/lvmp07
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 640
Allocated PE 640
Used PV 4

LVName /dev/vgclwss/lvmp08
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 640
Allocated PE 640
Used PV 4

LVName /dev/vgclwss/lvwsst01
LV Status available/syncd
LV Size (Mbytes) 20480
Current LE 1280
Allocated PE 1280
Used PV 6

LVName /dev/vgclwss/lvrmanwss
LV Status available/syncd
LV Size (Mbytes) 296960
Current LE 18560
Allocated PE 18560
Used PV 9

--- Physical volumes ---
PV Name /dev/dsk/c12t0d3
PV Name /dev/dsk/c14t0d3 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t0d4
PV Name /dev/dsk/c14t0d4 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t0d5
PV Name /dev/dsk/c14t0d5 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t0d6
PV Name /dev/dsk/c14t0d6 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t1d0
PV Name /dev/dsk/c14t1d0 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t1d1
PV Name /dev/dsk/c14t1d1 Alternate Link
PV Status available
Total PE 3235
Free PE 315
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t1d2
PV Name /dev/dsk/c14t1d2 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t1d3
PV Name /dev/dsk/c14t1d3 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c12t3d5
PV Name /dev/dsk/c14t3d5 Alternate Link
PV Status available
Total PE 3235
Free PE 0
Autoswitch On
Proactive Polling On

root@ugos388#

Re: Cannot extend filesystem

Jdamian — Fri, 16 Nov 2007 08:10:52 GMT

Your LV is PVG-distributed, but there is just ONE PV having free PEs. Therefore, you cannot extend the LV unless you change the allocation policy

Re: Cannot extend filesystem

Duncan Edmonstone — Fri, 16 Nov 2007 09:36:05 GMT

Methinks someone has extended to volume group to fit this LV in without fully understanding the implications:

/dev/vgclwss/lvrmanwss

I'm guessing an additional LUN was added to the VG to fully accomodate this LV, but no-one checked the existing layout of LVs in the VG.

To understand the way this was configured - read the man page for lvcreate pating particular attention to the comments on distributed allocation policy.

You can do the quick and dirty think which is to remove PVG-strict and ditributed allocation from the LV using

lvchange -D n -s y /dev/vgclwdd/lvmp07

which will result in completely unbalanced IO to any filesystem on the LV.

Or you can do the *right* thing which would be to:

a) move the /dev/vgclwss/lvrmanwss logical volume out to another volume group entirely (can't imagine why you'd want your backup on the same LUNs as your database anyway...

b) drop the number of disks in the VG back to 8 or extend the number of disks in the LV to 12

c) review your whole LVM configuration as the chances are this has happened elsehwere as well...

HTH

Duncan

Re: Cannot extend filesystem

WSS — Mon, 19 Nov 2007 13:38:46 GMT

Duncan,

Thanks for your advice much appreciated! The right thing to do is definately the best option, but obvioulsy a more pain stakingly one.

The reason we have lvrmanwss on the same VG as the core database is to easily fail it over as that VG gets failed over in a SG failover.

We could always create a new VG to get failed over as well, so that's not a problem.

I don't really want to risk additional I/O on that VG as that could cause additional issues.

I need to research this now and book some weekend time to do this!!

Thanks for you advice, as always, much appreciated... Points will be awarded :-)

Re: Cannot extend filesystem

WSS — Thu, 22 Nov 2007 14:59:47 GMT

Here's what I did to fix this issue. With help from HP Supoprt....

It's was pretty simple in the end...

The file /etc/lvmpvg was empty, for some reason had no info in it. I populated it with the following info (all the PV's in the VG and some initial config at the start) and I was able to extend the LV and filesystem.

# vi /etc/lvmpvg
#Added this -

VG /dev/vgclwss
PVG PVG0
/dev/dsk/c12t0d3
/dev/dsk/c12t0d4
/dev/dsk/c12t0d5
/dev/dsk/c12t0d6
/dev/dsk/c12t1d0
/dev/dsk/c12t1d1
/dev/dsk/c12t1d2
/dev/dsk/c12t1d3
/dev/dsk/c12t3d5

So once this file was populated with the above data, I was able to extend the LV.

Thanks for your input guys.

Regards,
Trevor McLachlan