There is discrepancy between lvdisplay size information and df, but comparing to other mount points (other lvs), the difference is common.

Thank you Sir.

Thanks for the comment. If you’ve already ran lvextend then what you’ll want to do is do an ext2online /dev/mapper/VolGroup00-LogVol06

Which will extend the actual filesystem to the new size which is indicated via the lvdisplay.

Let me know if you have any questions.

I see that you only mention about reducing the lv.

I tried to extend one of my lv. and using lvdisplay, I can see that the size already extend. (from 250GB t0 390GB). But, using df I can only see 250GB (the original size). What is wrong? and what should I do?

This is out put from df -h

/dev/mapper/VolGroup00-LogVol06
250G 231G 7.2G 97% /oracle

and this is output from lvdisplay

— Logical volume —
LV Name /dev/VolGroup00/LogVol06
VG Name VolGroup00
LV UUID 1AVRAH-nZaV-Vvia-26Ev-REdh-T0KT-KPBNsS
LV Write Access read/write
LV Status available
# open 1
LV Size 390.66 GB
Current LE 12501
Segments 3
Allocation inherit
Read ahead sectors 0
Block device 253:2

Thanks,

Dapid Candra

NOTE : This article come with ABSOLUTELY NO WARRANTY about any data loss. Rember to do a FULL BACKUP of your filesystem every time you need to expand/shrink them. Here you are an how-to for shrink ext3 partitions. NOTE : You can’t perform on-line…