1829594 Members
1606 Online
109992 Solutions
New Discussion

Re: lvextend !!

 
Ivan Azuara
Regular Advisor

lvextend !!

Hi !!

I need to extend the size about my File Systems /usr and /var to the double space.

My vg00 have 3 physical disks that 2 Gbytes each one. All my file systems are stripped in 3 disks into the vg00.

I know the procedure to extend file systems about vg00.

a) boot the server in single user (hpux -isl).
b) lvextend -L new_size /dev/vg00/lvol8

c) In theory the file system must be extended.

But, that??s false because send me the next message:

lvextend: Not enough free physical extents available.
lvextend: Couldn??t retrieve the list of the physical volumes belowging to volume group "/dev/vg00"
Failure possibly caused by strict allocation policy

I understand the error because one of my disks doesn??t have PE free in the boot disk

How can I extend this File Systems ?.

P.D. I attach the information about my server.

Thank??s !!

"Enjoy the life .."
9 REPLIES 9
Timothy Czarnik
Esteemed Contributor

Re: lvextend !!

Ivan,

This may be simplistic, but create a make_recovery tape, then recreate vg00 using that. You can resize vg00 filesystem size during the process.

Make sure you have 2 good make_recovery tapes and successful backups before starting this just in case!.

-Tim
Hey! Who turned out the lights!
Joseph Chakkery
Valued Contributor

Re: lvextend !!

No attachment seen.

Joe
Knowledge is wealth
Frederic Sevestre
Honored Contributor

Re: lvextend !!

Hi,
to extend a LV stripped on 3 disks, you need to have space on 3 differents disks.
You can used pvmove to free some pe on a full disk to have enough space for your stripped LV
Fr??d??ric
Crime doesn't pay...does that mean that my job is a crime ?
James R. Ferguson
Acclaimed Contributor

Re: lvextend !!

Hi Ivan:

If all of the existing disk have free physical extents available in sufficient quantity to equally add new extents, then no new disk need to be added to a striped configuration to extend a logical volume. However, if this is not the case, you need to add more physical disk ('vgextend') so that the strict allocation policy is satisfied. The number of disks used for extending the volume *must* equal the number of disks already striped across. This would appear to be your problem.

The Ignite recovery/install option is one way around your situtation.

I would urge you to consider replacing your multi-physical-disk vg00 configuration with a *single* physical disk which you then mirror.

Regards!

...JRF...
eran maor
Honored Contributor

Re: lvextend !!

Hi

can you give some info about the vg and the logical volume .
like the say the easier way to change the file system /var and /usr it to do a ignite backup and then to do a restore because over there you can choose to resize the file system size .

i think that mybe the problem in the lvextend it that the logical volume is a mirror or stripe , and it can cause the problem .

it will be much easier with the data ( vgdisplay -v vg0 and lvdisplay to the /var and /usr )
love computers
Bill McNAMARA_1
Honored Contributor

Re: lvextend !!

try lvchange -s n /dev/vg00/lvol8
then
lvextend.

It may not want to be extended outside of the current PV it's on.

Or perhaps you got mirroring on and the only free space in the vg is on one PV.

For a fix quick,
post up
lvdisplay -v /dev/vg00/lvol8

Later,
Bill
It works for me (tm)
Sanjay_6
Honored Contributor

Re: lvextend !!

Patrick Wallek
Honored Contributor

Re: lvextend !!

Why do you have your VG00 lvols striped? Even if they span multiple disks, I don't think striping any vg00 stuff is going to give you a whole lot of performance gain.

I would seriously consider Jim Fergusons suggestion about getting 2 larger disks (9 or 18 GB) to use as your VG00 disks and then mirror them. You'll have redundency and not have to worry about striping or problems extending and of the LVs (other than /, pri. swap and /stand).
Dave Wherry
Esteemed Contributor

Re: lvextend !!

I'll jump on the bandwagon with Jim and Patrick and suggest you rebuild vg00 using larger, mirrored disks. Also, Tim's suggestion of using make_recovery makes the process very easy and quick.
To add a little more, think about splitting out some of the directories into new file systems. For example, make a new file system /var/adm/crash. If you have system problems /var will not fill up with the dump. It's kept segregated to another file system. If you print a lot on this system you can create another file system for /var/spool. Some applications that go in /var/opt can be seperated out. Such as a new file system for /var/opt/omni. There may be other candidates on your system. Take a look.