Can't extend lv

Linux and Unix-Like Red Hat
1

Hi,

I have recently increased the size of my pv and I am now attempting to increase the lv but I get the following error:

# vgdisplay
  --- Volume group ---
  VG Name               VolGroup00
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  16
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                8
  Open LV               8
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               249.97 GB
  PE Size               32.00 MB
  Total PE              7999
  Alloc PE / Size       2013 / 62.91 GB
  Free  PE / Size       5986 / 187.06 GB
  VG UUID               Zme52J-J22F-PisG-oOSQ-wwB2-QJ29-ZpofJk
   
# lvextend -L +180G /dev/VolGroup00/lvol0
  Extending logical volume lvol0 to 205.00 GB
  device-mapper: reload ioctl failed: Invalid argument
  Failed to suspend lvol0

Any ideas on how I can resolve this?

R,
D.

2

How did you increase the size of the PV?

I don't think the VG is aware of dynamic PV resizing.

Is the VG using a single disk?

It would be helpful to see the output of pvdisplay and lvdisplay as well.

Edit: Also, is it a real server or a virtualized environment?

3

Do you need to

unmount

before this?

4

Hi,

I have tried umounting this and it doesn't make a difference.

# pvdisplay
  --- Physical volume ---
  PV Name               /dev/cciss/c0d0p5
  VG Name               VolGroup00
  PV Size               250.00 GB / not usable 31.81 MB
  Allocatable           yes 
  PE Size (KByte)       32768
  Total PE              7999
  Free PE               5986
  Allocated PE          2013
  PV UUID               yU2Opq-vt11-nlmX-Evwa-RKv1-0H3O-pxRg

I ran the following command in order to resize the physical volume:

# pvresize --setphysicalvolumesize 250G /dev/cciss/c0d0p5

This is a BL460c blade server with hardware RAID1.

R,
D.

5

can u put that complete command

6

I assume you are referring to the pvresize command? That is the complete command.

7

This is a shot in the dark, but looks like there are flags to vgchange that might fix this.

--refresh
If any logical volume in the volume group is active, reload its
metadata. This is not necessary in normal operation, but may be
useful if something has gone wrong or if you're doing clustering
manually without a clustered lock manager.

-x, --resizeable {y|n}
Enables or disables the extension/reduction of this volume group
with/by physical volumes.

8

Hi,

Ok thanks for the feedback but I have already attempted this and it didn't help.

I have now resolved the issue by rebuilding the server having performed a full backup on the box.

This issue presented itself after a hardware upgrade on a blade server and extending the logical drive via the ACU (Array Configuration Utility) on the SMART Array Controller; hence the pvresize on the OS.

My advise is do NOT extend the logical drive, simply opt to create a new logical drive. I have done this many times and there has never been an issue. You live and learn eh?

Regards,
D.