lvextend generating error not enough free space

[Staci Tribelhorn]

In the attachment I have displayed the output from the commands - lvdisplay /dev/vgdata/sbdata and
vgdisplay -v /dev/vgdata

As noted in the vgdisplay, there are 26,142 free physical extents for this volume group; however, when I attempt to extend the /dev/vgdata/sbdata volume from 6000 LE to 7800 LE I get the error 'lvextend: Not enough free physical extents available'. I've also attempted to extend with 6600 LE and still get the same error. It's as though the system isn't recognizing the available free space.

This volume group is allocated over a mirrored 6 disk set and I've run diagnostics on all of the disks with success. Back in July we moved the SCSI cards for these disk trays from the Turbo slots to non-turbo slots, so I'm thinking maybe we have a configuration file that is still looking for the old disk addresses???

Any suggestions on how to solve this dilemma is greatly appreciated.

Thanks,
Staci

[Coolmar]

Hi Staci,

Please see the following thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1067945

Your "allocation" is strict/distributed and I believe doing an lvchange and then lvextend (as per the last entry in the thread) might fix your problem.

[Staci Tribelhorn]

Hum, since installing OnlineJFS 4 years ago years ago, I've never had to do an lvchange prior to an lvextend. Thanks for the information. I'll look into it.

[John Guster]

each disk has more than 1800 PE free. It should let you extend the LV. Do lvdisplay to see which disks are used for this lv, then lvexstend -l 7800 /dev/vgdata/sbdata /dev/dsk/c?t?d?

lvextend -m 1 /dev/vgdata/sbdata /dev/dsk/c#t#d# for the mirror disk.

Cheers.

[James R. Ferguson]

Hi Staci:

Your allocation of PVG-strict/distributed means that consecutive logical extents must reside on different physical volumes, *and* that no mirror copies can reside on the same physical volume.

Thus, you do not have free physical extents that satisfy this constraint.

An 'lvdisplay -v' will reveal the actual extent mappings. Your '/etc/lvmpvg' configuration file is designed to assist in mirror copy creation. See the manpages for 'lvmpvg(4)'. When properly setup, use this file with 'lvextend' instead of specifying the pv_path.

Regards!

...JRF...

[George Liu_4]

from lvdisplay, check to see any allocation restrict such as strict/contiguous. If there is such restriction, remove it if appropriate. Then try lvextend again

[Staci Tribelhorn]

James,

I'm afraid to ask, but...could my problem be resolved by simply adding the PVG information to the /etc/lvmpvg file as follows:

VG /dev/vgdata
PVG PV1
/dev/dsk/c6t8d0
/dev/dsk/c6t9d0
/dev/dsk/c6t10d0
/dev/dsk/c6t11d0
/dev/dsk/c6t12d0
/dev/dsk/c6t14d0
PVG PV2
/dev/dsk/c7t8d0
/dev/dsk/c7t9d0
/dev/dsk/c7t10d0
/dev/dsk/c7t11d0
/dev/dsk/c7t12d0
/dev/dsk/c7t14d0

...or is this going to screw up my mirroring?

[Deoncia Grayson_1]

Before creating your pvg file, just make sure the disks are on two different frames and not pointing to the same disks. If they are broken out correctly then it should work fine.

[James R. Ferguson]

Hi (again) Staci:

> I'm afraid to ask, but...could my problem be resolved by simply adding the PVG information to the /etc/lvmpvg file as follows:

Assuming the your 'lvmpvg' file matches the physical extent distribution of the mirrored extents, yes, specifying the pvg_name instead of the pv_path(es) in your 'lvextend -m ' mirror operation may be all that is needed to accomodate your needs.

Once again, a 'lvdisplay -v' for the logical volume in question will show you the distribution of physical extents among their various physical volumes.

Regards!

...JRF...

[Staci Tribelhorn]

Thanks to everyone for your suggestions. Editing the /etc/lvmpvg file resolved this particular problem. Thanks James.

[Staci Tribelhorn]

Editing the /etc/lvmpvg file resolved this issue.