From: Andreas Dilger <adilger@turbolinux.com>
To: "Eric M. Hopper" <hopper@omnifarious.mn.org>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] lvdisplay disagrees with df for resized LV
Date: Thu, 12 Oct 2000 12:41:21 -0400 (EDT) [thread overview]
Message-ID: <200010121641.MAA03003@lynx.turbolabs.com> (raw)
In-Reply-To: <20001011084555.A6983@omnifarious.mn.org> from "Eric M. Hopper" at Oct 11, 2000 08:45:55 AM
Eric M. Hopper writes:
> On Wed, Oct 11, 2000 at 01:25:50PM +0100, Andy Cowling wrote:
> > I'm just starting out using LVM under SuSE 7.0. I created a logical
> > volume which was initially 30Gb but I then resized it to 90Gb (using
> > lvresize) spanning 3 physical volumes each of 30Gb.
> >
> > Now, lvdisplay/vgdisplay shows the LV/VG size as 90Gb, but df still
> > lists the file system as 30Gb.
> >
> > How can I get df to recognise the addtional space ?
>
> I'm assume the filesystem is an ext2 filesystem. If it is, then
> you need to find an ext2 resizing utility. resize2fs is one such
> utility. I'm not sure where to find them on the web, but they
> definitely exist.
You can get ext2 resizing tools from ext2resize.sourceforge.net. There
is also the resize2fs tool included with e2fsprogs 1.19.
> In general, the filesystem can only be resized when it's
> offline. The filesystem resizing utility updates all the filesystem
> data structures to reflect the new size, and creates new data structures
> in the new space.
With the ext2online kernel patch and user-space tool, you can do online
(mounted) ext2 resizes.
Cheers, Andreas
next prev parent reply other threads:[~2000-10-12 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-11 12:25 [linux-lvm] lvdisplay disagrees with df for resized LV Andy Cowling
2000-10-11 13:45 ` Eric M. Hopper
2000-10-11 16:28 ` Andy Cowling
2000-10-11 17:20 ` Eric M. Hopper
2000-10-11 17:57 ` Charles Duffy
2000-10-11 18:26 ` Brian Poole
2000-10-12 16:41 ` Andreas Dilger [this message]
2000-10-11 14:12 ` Les Hazelton
2000-10-11 15:38 Rochelle Lakey
2020-11-27 16:17 Holger Grothe
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=200010121641.MAA03003@lynx.turbolabs.com \
--to=adilger@turbolinux.com \
--cc=hopper@omnifarious.mn.org \
--cc=linux-lvm@msede.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;
as well as URLs for NNTP newsgroup(s).