archive mirror
 help / color / mirror / Atom feed
From: "Eric M. Hopper" <>
Subject: Re: [linux-lvm] lvdisplay disagrees with df for resized LV
Date: Wed, 11 Oct 2000 08:45:55 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <m2u2ajmunl.fsf@puma.redeye>; from on Wed, Oct 11, 2000 at 01:25:50PM +0100

[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]

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.

	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.  df bases it's output on what the filesystem says
about the size, not the block device itself.

	It might be that SUSE came with a resizing utility.  I'd
actually rather expect it if they also packaged LVM.

Have fun (if at all possible),
The best we can hope for concerning the people at large is that they
be properly armed.  -- Alexander Hamilton
-- Eric Hopper ( --

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2000-10-11 13:45 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 [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).