topic Re: lvextend error in Operating System - HP-UX

lvextend error

Nobody's Hero — Wed, 17 Dec 2003 08:31:29 GMT

Hi All,
I am in the middle of mirroring my root drive on an 11.0 system. My secondary root drive failed. I am familiar with all the steps to mirror a drive properly however I am getting an error this time. vg00 primary and vg00 secondary disks are the same size, 9Gbytes. when trying to entend a mirror copy of lvol6(/tmp), I get the following error:

lvextend -m 1 /dev/vg00/lvol6 /dev/dsk/c0t5d0
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lvol6" could not be extended.
Failure possibly caused by strict allocation policy

Caused by one mirror disk having more free extents than the other mirror copy. How can one disk have a difference if they are both the same size? I dont want to turn of "strick allocation" because of the obvious.

10x
RPM

Re: lvextend error

Mark Grant — Wed, 17 Dec 2003 08:36:14 GMT

Well, maybe not all logical volumes have strict allocation and therefore you have a primary and mirror of bits of the same logical volume on the second disk. I think you should do a pvdisplay -v on all the disks to see which extents have been placed where.

Re: lvextend error

Pete Randall — Wed, 17 Dec 2003 08:36:37 GMT

Robert,

Can you post the output of vgdisplay -v vg00 and pvdisplay /dev/dsk/cXtXdX and pvdisplay /dev/dsk/cYtYdY (both of the mirrors, in other words)?

Pete

Re: lvextend error

Jeff Schussele — Wed, 17 Dec 2003 08:37:20 GMT

Hi RPM,

I think you may be misunderstanding "strict allocation". You NEED to have this on as it causes the mirror pairs to be on different disks. With it off you can have both mirror pairs on the same disk & if that disk fails - game's over.
You need to restart the mirror process after lvreducing the already mirrored LVs and then lvchange -s y /dev/vg00/lvolX
to set the allocation policy to strict

Run
lvdisplay -v /dev/vg00/lvolX | more
and you'll see that the pairs are actually on the same disk - not a good thing.

Rgds,
Jeff

Re: lvextend error

Nobody's Hero — Wed, 17 Dec 2003 08:37:25 GMT

That is the 1st thing I did Mark and I dont see any problems. Looking again.....

Re: lvextend error

T G Manikandan — Wed, 17 Dec 2003 08:38:10 GMT

The problem here is,

you have the same size disks.

you have some volumes mirrored.
Also you have some other volumes which are non-mirrored.
Mirrored volumes take space on both the disks and non-mirrored volumes take space on only the one disk.
So lvextend pops up this error.
what you can do is you can add additional disks to the VG.

Or
you can move the non-mirrored lv's to some other VG(other disks)

thanks

Re: lvextend error

G. Vrijhoeven — Wed, 17 Dec 2003 08:38:48 GMT

Hi,

You can use pvdisplay -v /dev/dsk/c?t?d? to view if the problem is related to strict allocation.

PV Name /dev/dsk/c1t6d0
VG Name /dev/vg00
PV Status available
Allocatable yes
VGDA 2
Cur LV 11
PE Size (Mbytes) 16
Total PE 4374
Free PE 1248
Allocated PE 3126
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol1 6 6
/dev/vg00/lvol2 640 640
/dev/vg00/lvol3 16 16
/dev/vg00/lvol4 128 128
/dev/vg00/lvol5 128 128
/dev/vg00/lvol6 128 128
/dev/vg00/lvol7 128 128
/dev/vg00/lvol9 25 25
/dev/vg00/lvol10 640 640
/dev/vg00/lvol11 1280 1280

--- Physical extents ---
PE Status LV LE
0000 current /dev/vg00/lvol1 0000
0001 current /dev/vg00/lvol1 0001
0002 current /dev/vg00/lvol1 0002
0003 current /dev/vg00/lvol1 0003
0004 current /dev/vg00/lvol1 0004
0005 current /dev/vg00/lvol1 0005
0006 current /dev/vg00/lvol2 0000
0007 current /dev/vg00/lvol2 0001
0008 current /dev/vg00/lvol2 0002
0009 current /dev/vg00/lvol2 0003
0010 current /dev/vg00/lvol2 0004
0011 current /dev/vg00/lvol2 0005
0012 current /dev/vg00/lvol2 000
...... etc.

Gideon

Re: lvextend error

Pete Randall — Wed, 17 Dec 2003 08:38:49 GMT

Robert,

On that pvdisplay, make it pvdisplay -v but don't include all the "--- Physical extents ---" stuff.

Pete

Re: lvextend error

Nobody's Hero — Wed, 17 Dec 2003 08:42:44 GMT

Of course, 6 is primary and 5 is mirror.
See attached

Re: lvextend error

Nobody's Hero — Wed, 17 Dec 2003 08:44:04 GMT

Re: lvextend error

Nobody's Hero — Wed, 17 Dec 2003 08:44:31 GMT

PV 6

Re: lvextend error

Nobody's Hero — Wed, 17 Dec 2003 08:44:58 GMT

PV 5

Re: lvextend error

Lorenzo Facello — Wed, 17 Dec 2003 08:45:37 GMT

Hi,
try to verify the disk's size:
diskinfo -v /dev/rdsk/cxtxdx

and

verify that your lvol6 is ok!
lvdisplay -v /dev/vg00/lvol6
fsck -V
Hope this Helps.
L.

Re: lvextend error

T G Manikandan — Wed, 17 Dec 2003 08:49:04 GMT

unmirrored lv's
dev/vg00/lvol7
/dev/vg00/lvol8
only are on the first disk.

Re: lvextend error

Pete Randall — Wed, 17 Dec 2003 08:52:21 GMT

Robert,

There are two other PV's, according to your vgdisplay, AND, I don't see lvol 6 on either pv5 or pv6!!

Pete

Re: lvextend error

Lorenzo Facello — Wed, 17 Dec 2003 08:53:07 GMT

can I have the bdf output??

Re: lvextend error

Pete Randall — Wed, 17 Dec 2003 08:55:44 GMT

Robert,

My conclusion at this point is that lvol6 resides on pv4 (c0t4d0) and pv3 (c0t3d0). The problem is that pv4 is completely full.

Pete

Re: lvextend error

Nobody's Hero — Wed, 17 Dec 2003 08:58:13 GMT

I understand that lv 7 and 8 are not done yet. My lvextend error happened while extending lv 6.

Re: lvextend error

Lorenzo Facello — Wed, 17 Dec 2003 08:59:34 GMT

you have x file system on PVx, this PVx is full. I think there was a confiruation error at the moment of vg00 creation

Re: lvextend error

Nobody's Hero — Wed, 17 Dec 2003 09:00:05 GMT

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 159744 98614 57319 63% /
/dev/vg00/lvol1 143573 23291 105924 18% /stand
/dev/vg00/lvol8 1572864 1185755 362998 77% /var
/dev/vg00/lvol7 2129920 708515 1332613 35% /usr
/dev/vg00/lvol6 2060288 4338 1930124 0% /tmp
/dev/vg02/lvol1 64811008 13903528 50509776 22% /pluto_archive_NFS2
/dev/vg01/lvol1 64811008 46837256 17833392 72% /pluto_archive_NFS1
/dev/vg00/lvol5 2129920 2090558 39362 98% /opt
/dev/vg00/lvol13 1716224 1400837 297803 82% /home
pluto:/u 35543812 16320765 19223047 46% /pluto_data