df doesn't display increased available disk space

linux-lvm Robert Buick 3 participants 7 messages Mar 3, 2005 – Mar 4, 2005

Share & tools

Robert Buick

author

2005-03-03 21:36 UTC #0 lore raw

I'm running Fedora Core 3 with LVM2, and have added /dev/hda4 (13.09GB) to the VG, however this increase is not reflected if I do a df -h. Have I missed something?

Thanks for your time,

Rob Buick

[root@stemme mapper]# lvscan
ACTIVE '/dev/VolGroup00/LogVol00' [34.53 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
[root@stemme mapper]# pvscan

  PV /dev/hda2   VG VolGroup00   lvm2 [23.41 GB / 32.00 MB free]
  PV /dev/hda4   VG VolGroup00   lvm2 [13.09 GB / 0    free]

Total: 2 [36.50 GB] / in use: 2 [36.50 GB] / in no VG: 0 [0 ]
[root@stemme mapper]# vgscan
Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2
[root@stemme mapper]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00

                       22G  9.0G   12G  45% /
/dev/hda1              99M   22M   73M  23% /boot

none 760M 0 760M 0% /dev/shm

Erik Ohrnberger

2005-03-03 21:43 UTC #1 lore raw

Don't you have to expand the filesystem before df -h will see it as available free space in the filesystem?

Quoted 33 lines · Robert Buick

I'm running Fedora Core 3 with LVM2, and have added /dev/hda4 (13.09GB) to the VG, however this increase is not reflected if I do a df -h. Have I missed something?
Thanks for your time,
Rob Buick
[root@stemme mapper]# lvscan
ACTIVE '/dev/VolGroup00/LogVol00' [34.53 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
[root@stemme mapper]# pvscan
  PV /dev/hda2   VG VolGroup00   lvm2 [23.41 GB / 32.00 MB free]
  PV /dev/hda4   VG VolGroup00   lvm2 [13.09 GB / 0    free]
Total: 2 [36.50 GB] / in use: 2 [36.50 GB] / in no VG: 0 [0 ]
[root@stemme mapper]# vgscan
Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2
[root@stemme mapper]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                       22G  9.0G   12G  45% /
/dev/hda1              99M   22M   73M  23% /boot
none 760M 0 760M 0% /dev/shm
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Robin Green

2005-03-03 21:47 UTC #2 lore raw

In reply to Robert Buick

Quoted 3 lines · Robert Buick

I'm running Fedora Core 3 with LVM2, and have added /dev/hda4 (13.09GB) to the VG, however this increase is not reflected if I do a df -h. Have I missed something?

Yes - you need to resize the filesystem as well.

If you are using an ext2 or ext3 filesystem you could use resize2fs. If you are using reiserfs, you could use resize_reiserfs. I don't know about resize tools for other filesystems.

Please note that resize2fs in Fedora Core 3 is buggy, and may corrupt the
resize inode. To get a version that works better, I recommend you download and build from source e2fsprogs 1.36 from http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.36.tar.gz

(If you wanted to avoid using resize2fs altogether, you could of course backup all your data in /, mke2fs the root filesystem, and copy all the data back again. But that would be much slower.)

Signature · 1 line

Robin

Robert Buick

author

2005-03-04 18:35 UTC #3 lore raw

I'm using type 8e, does anyone happen to know if resize2fs is appropriate for this type; the man page only mentions type2.

Quoted 35 lines · Robin Green

Quoted 17 lines · Robert Buick
I'm running Fedora Core 3 with LVM2, and have added /dev/hda4 (13.09GB) to the VG, however this increase is not reflected if I do a df -h. Have I missed something?
[root@stemme mapper]# lvscan
ACTIVE '/dev/VolGroup00/LogVol00' [34.53 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
[root@stemme mapper]# pvscan
PV /dev/hda2 VG VolGroup00 lvm2 [23.41 GB / 32.00 MB free]
PV /dev/hda4 VG VolGroup00 lvm2 [13.09 GB / 0 free]
Total: 2 [36.50 GB] / in use: 2 [36.50 GB] / in no VG: 0 [0 ]
[root@stemme mapper]# vgscan
Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2
[root@stemme mapper]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
Quoted 3 lines
                      22G  9.0G   12G  45% /
/dev/hda1 99M 22M 73M 23% /boot
none 760M 0 760M 0% /dev/shm
Yes - you need to resize the filesystem as well.
If you are using an ext2 or ext3 filesystem you could use resize2fs. If you are using reiserfs, you could use resize_reiserfs. I don't know about resize tools for other filesystems.
Please note that resize2fs in Fedora Core 3 is buggy, and may corrupt the
resize inode. To get a version that works better, I recommend you download and build from source e2fsprogs 1.36 from http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.36.tar.gz
(If you wanted to avoid using resize2fs altogether, you could of course backup all your data in /, mke2fs the root filesystem, and copy all the data back again. But that would be much slower.)

Erik Ohrnberger

2005-03-04 18:42 UTC #4 lore raw

Robert,
When you say type 8e, it makes me think of the partition table, not
the filesystem, which would be etx2 or etx3 or XFS or Reiserfs or ....

Now when a partition is marked as type 8e, it is an LVM partition.

Best of luck,
Erik.

Quoted 57 lines · Robert Buick

I'm using type 8e, does anyone happen to know if resize2fs is appropriate for this type; the man page only mentions type2.
Quoted 39 lines · Robin Green
Quoted 1 line · Robert Buick
I'm running Fedora Core 3 with LVM2, and have added /dev/hda4
(13.09GB)
Quoted 1 line
to the VG, however this increase is not reflected if I do a df -h.
Have
Quoted 15 lines
I missed something?
[root@stemme mapper]# lvscan
ACTIVE '/dev/VolGroup00/LogVol00' [34.53 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
[root@stemme mapper]# pvscan
PV /dev/hda2 VG VolGroup00 lvm2 [23.41 GB / 32.00 MB free]
PV /dev/hda4 VG VolGroup00 lvm2 [13.09 GB / 0 free]
Total: 2 [36.50 GB] / in use: 2 [36.50 GB] / in no VG: 0 [0 ]
[root@stemme mapper]# vgscan
Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2
[root@stemme mapper]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
Quoted 3 lines
                      22G  9.0G   12G  45% /
/dev/hda1 99M 22M 73M 23% /boot
none 760M 0 760M 0% /dev/shm
Yes - you need to resize the filesystem as well.
If you are using an ext2 or ext3 filesystem you could use resize2fs. If you
are using reiserfs, you could use resize_reiserfs. I don't know about resize
tools for other filesystems.
Please note that resize2fs in Fedora Core 3 is buggy, and may corrupt the
resize inode. To get a version that works better, I recommend you download and build
from source e2fsprogs 1.36 from
http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.36.tar.gz
Quoted 4 lines
(If you wanted to avoid using resize2fs altogether, you could of course backup all your data in /, mke2fs the root filesystem, and copy all the data
back again. But that would be much slower.)
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Erik Ohrnberger

2005-03-04 19:19 UTC #5 lore raw

Robert,
You need to change one of the top most levels (filesystem). Read this
next part from the bottom up (Everyone: if I have something here wrong, let me know)

Highest Level: File System layer (files & directories)
LVM LV Layer (logical volumes)
LVM PV layer (physical volumes)
Partition table (special data on the hard disk) LBA translation (in disk controller or drive circutry)
Lowest Level: Physical Hard disk (platter that spins & r/w heads)

OK, so like it sounds like you've added more space to the LVM PV
layer. So like you need to add it to the LVM LV layer, and then you need to change the file system size to take advantage of the increased LVM LV space that you've added.

Clear as mud, right?

Quoted 75 lines · Erik Ohrnberger

Robert,
When you say type 8e, it makes me think of the partition table, not
the filesystem, which would be etx2 or etx3 or XFS or Reiserfs or ....
Now when a partition is marked as type 8e, it is an LVM partition.
Best of luck,
Erik.
Quoted 51 lines · Robert Buick
I'm using type 8e, does anyone happen to know if resize2fs is appropriate for this type; the man page only mentions type2.
Quoted 39 lines · Robin Green
Quoted 1 line · Robert Buick
I'm running Fedora Core 3 with LVM2, and have added /dev/hda4
(13.09GB)
Quoted 1 line
to the VG, however this increase is not reflected if I do a df -h.
Have
Quoted 15 lines
I missed something?
[root@stemme mapper]# lvscan
ACTIVE '/dev/VolGroup00/LogVol00' [34.53 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
[root@stemme mapper]# pvscan
PV /dev/hda2 VG VolGroup00 lvm2 [23.41 GB / 32.00 MB free]
PV /dev/hda4 VG VolGroup00 lvm2 [13.09 GB / 0 free]
Total: 2 [36.50 GB] / in use: 2 [36.50 GB] / in no VG: 0 [0 ]
[root@stemme mapper]# vgscan
Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2
[root@stemme mapper]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
Quoted 3 lines
                      22G  9.0G   12G  45% /
/dev/hda1 99M 22M 73M 23% /boot
none 760M 0 760M 0% /dev/shm
Yes - you need to resize the filesystem as well.
If you are using an ext2 or ext3 filesystem you could use resize2fs. If you
are using reiserfs, you could use resize_reiserfs. I don't know about resize
tools for other filesystems.
Please note that resize2fs in Fedora Core 3 is buggy, and may corrupt the
resize inode. To get a version that works better, I recommend you download and build
from source e2fsprogs 1.36 from
http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.36.tar.gz
Quoted 4 lines
(If you wanted to avoid using resize2fs altogether, you could of course backup all your data in /, mke2fs the root filesystem, and copy all the data
back again. But that would be much slower.)
Quoted 6 lines
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Robin Green

2005-03-04 19:07 UTC #6 lore raw

In reply to Robert Buick

I think you are making a potentially very dangerous mistake!

Type 8e is a partition type. You don't want to use resize2fs on the PARTITION, which is not an ext2 partition, but an lvm partition. You want
to resize the filesystem on the logical VOLUME.

And yes, resize2fs is appropriate for logical volumes. But resize the VOLUME (e.g. /dev/VolGroup00/LogVol00), not the partition or volume group.

Quoted 2 lines · Robert Buick

I'm using type 8e, does anyone happen to know if resize2fs is appropriate for this type; the man page only mentions type2.