Problems extending /

[go3mon]

I have this message:
I must extend / root fs because it is at 91%

omih567 root / :vgdisplay vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 15
Open LV 15
Max PV 16
Cur PV 6
Act PV 6
Max PE per PV 4350
VGDA 12
PE Size (Mbytes) 8
Total PE 26040
Alloc PE 19930
Free PE 6110
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

omih567 root / :lvdisplay /dev/vg00/lvol3
--- Logical volumes ---
LV Name /dev/vg00/lvol3
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 304
Current LE 38
Allocated PE 76
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

omih567 root / :lvextend -L 504 /dev/vg00/lvol3
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lvol3" could not be extended.
Failure possibly caused by contiguous allocation policy.
Failure possibly caused by strict allocation policy
omih567 root / :lvextend -L 404 /dev/vg00/lvol3
Warning: rounding up logical volume size to extent boundary at size "408" MB.
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lvol3" could not be extended.
Failure possibly caused by contiguous allocation policy.
Failure possibly caused by strict allocation policy

I have more Free PE, why have this message?

[Florian Heigl (new acc)]

Because the root volume requires to be contiguous. Probably your disks look look this

lvol1
lvol2
lvol3 /
lvol4
[...]
lvol10
[FREE SPACE]

if You know how, you can fix this by changing it the layout a bit so that it looks like the following:

lvol1
lvol2
lvol3 /
[little FREE SPACE]
[...]
lvol10
lvol4
[FREE SPACE]

This is the only safe way to do it online, but rather lenghty and you should do it on a test system first.

Other than that the options are:

- Restore from ignite image, increasing /
- move out /etc/lvmconf to an extra lv in lvm maint. mode
- simply clean up the / lvol (this is definitely the easiest choice)

Florian

[Bill Hassell · Accepted solution]

First rule of HP-UX sysadmin: never extend /

The / directory is static and never changes so your 300 meg / is more than enough. The reason that it is more than 20%-40% full is that one or more users have made serious mistakes. No matter how big you make /, even dozens of Gbytes will not be enough if you do not monitor disk space. It is the most common task for a sysadmin.

Now you can make an Ignite backup of the current system, then re-install it from the backup and resize everything (on second thought, make two backup tapes in case of problems). Or you can use some complicated (read: possibly unsuccessful) methods to replicate and move the first 3 lvols, or you can manage your space.

First rule in managing disk space: do NOT look for big files. You may have hundreds of small junk files in some directory that you'll never find that way. So look for big directories with du an sort:

du -kx / | sort -rn | head -20

Here is an example of normal systems (11.11):

83568 /
32840 /etc
32424 /sbin
14984 /etc/opt
12832 /etc/vx
10640 /etc/vx/type
8704 /etc/opt/resmon

Now there are variations of course. Here is an 11.23 Itanium system:

260752 /
139664 /sbin
120664 /etc
96096 /etc/vx
82712 /etc/vx/type
35536 /sbin/fs
34552 /etc/vx/type/static
21680 /etc/vx/type/gen
20904 /etc/opt
16280 /sbin/fs/vxfs

The important feature is that /etc and /sbin are always the largest directories. If you see anything else, that directory does not belong in /. A common spelling error will fill up /dev so look for ordinary files in /dev:

find /dev -type f

There will be no resukts from this command unless there are mistakes (like /dev/rmt/om). Once you find some big directories, sort the contents by size:

cd /some_dir
ll | sort -rnk5 | head

This is by far the safest way to manage disk space and no matter how much money you have to buy more disks, the system will need more unless the sysadmin manages disk space.

[ssudhir]

Hi,
As said earlier by one of our friend.
1. Taking ignite backup and restoring would be one of the safest way to make it possible.
2. There is another way is we can move lvol4 to some other disk using pvmove command (provided vg00 has multipile disk) . This will allow more space near lvol3 so you can comfortable extend lvol3.
3. You can try to find the large files in the / and house keep those file.

find / -size +50000 -xdev -exec ll {} \;

Will show you all the large files.

Regrads
S Sudhir.


Regrads
S Sudhir.