Problem in extending /tmp

[Nisar Ahmad]

Hi There

I am trying lvextend.

I have extended /usr filesystem no problem but I can't do for /tmp it is complaining like that:

# lvextend -L 800 /dev/vg00/lvol4
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lvol4" could not be extended.
Failure possibly caused by strict allocation policy


Where as details of the /tmp is:

# lvdisplay /dev/vg00/lvol4
--- Logical volumes ---
LV Name /dev/vg00/lvol4
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 120
Current LE 30
Allocated PE 60
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

Any clue will be appreciated.

Thanks

Nisar

[Patrick Wallek]

One possibility is you do not have enough free extents in the VG to extend /tmp to the size you want. Since you are mirrored either disk in the mirror could be the problem.

A 'vgdisplay -v /dev/vg00' and the exact lvextend command you are using would help in trying to diagnose your problem.

[Chris Vail]

You didn't post the pertinent information, which is whether or not you actually have the necessary PE available in volume group vg00. The command "vgdisplay /dev/vg00" will give you a multi-line report. If the entry for TOTAL PE matches ALLOC PE, then the FREE PE will be 0, which means that your system is out of space, and cannot be extended.

Chris

[Michael Tully]

The problem that you have is that lvol4 (/tmp) has been set up in strict allocation mode. What this means is that unless all the extents can be one after the other for the new size it will fail.
For (/tmp) I don't believe it is necessary should have a strict allocation policy.

# lvchange -s n /dev/vg00/lvol4

[Rajeev Shukla]

Possibly send the vgdisplay out put too. It feels that you are left with no space in /dev/vg00 and you'll have to add one more disk extend the VG and then extend the /tmp

Rajeev