From: Robin Green <greenrd@greenrd.org>
To: robert.buick@btconnect.com,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] df doesn't display increased available disk space
Date: Thu, 3 Mar 2005 21:47:32 +0000 [thread overview]
Message-ID: <20050303214732.GD4141@pob> (raw)
In-Reply-To: <1109885756.6400.16.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
On Thu, Mar 03, 2005 at 09:35:55PM +0000, Robert Buick wrote:
> 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.)
--
Robin
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-03 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 21:35 [linux-lvm] df doesn't display increased available disk space Robert Buick
2005-03-03 21:42 ` Erik Ohrnberger
2005-03-03 21:47 ` Robin Green [this message]
2005-03-04 18:35 ` Robert Buick
2005-03-04 18:40 ` Erik Ohrnberger
2005-03-04 19:18 ` Erik Ohrnberger
2005-03-04 19:07 ` Robin Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050303214732.GD4141@pob \
--to=greenrd@greenrd.org \
--cc=linux-lvm@redhat.com \
--cc=robert.buick@btconnect.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox