Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've done lvresize -L 264G 101/root (was 15GB) but /dev/mapper/101-root shows 13Gb. What am I doing wrong? I really appreciate the help!

root@server1:/home/user# df -h

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/101-root   13G  2.5G  9.5G  21% /
udev                 621M  4.0K  621M   1% /dev
tmpfs                 252M  296K  251M   1% /run
none                  5.0M     0  5.0M   0% /run/lock
none                  629M     0  629M   0% /run/shm
/dev/sda1             228M   26M  191M  12% /boot

root@server1:/home/user# lvs
LV     VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
root   101  -wi-ao 464.00g                                      
swap_1 101  -wi-ao   1.25g   
share|improve this question
up vote 1 down vote accepted

lvresize resize only LVM volume, but in df you view size of partition(ext4) you mast also resize partiton(not all partition support online resize).

# lvextend -L 20G VolGroup00/lvolhome (or lvresize -L +5G VolGroup00/lvolhome)
# resize2fs /dev/VolGroup00/lvolhome
share|improve this answer
Some terminology: It's the file system that needs to be resized, you don't usually have a partition table inside a logical volume. – Sven Mar 18 '13 at 13:37

Doing a lvresize is not sufficient, you need to enlarge the file system as well. How this is done is dependent on the type of filesystem (e.g. with xfs_growfs for XFS or resize2fs for ext3/ext4).

Make sure you have a backup before doing this.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.