All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] resizing logical volumes
Date: Wed Jul 10 08:32:02 2002	[thread overview]
Message-ID: <20020710133238.GC822@tykepenguin.com> (raw)
In-Reply-To: <3D2C3003.3090307@jumpline.com>

On Wed, Jul 10, 2002 at 09:00:51AM -0400, Ben Snyder wrote:
> OK, I asked a question here the other day that ended up being a 
> filesystems question, sorry, but thanks for removing my head from my 
> arse on that one (I knew that, really I did).
> 
> While I was asking that question, I also asked about adding existing 
> partitions on other devices to a logical volume/volume group.
> 
> The reply I got was this:
> 
> pvcreate /dev/device
> vgextend VolGroupName /dev/device
> lvextend --size +60G LogicalVolumePath
> 
> 
> This all seemed to work just fine, in fact when I do a lvdisplay and 
> vgdisplay, it says 120G (which is what I expected it to be).  However, 
> when I try to perform the e2fsadm, I get the following (and I'm not an 
> idiot, I'm using/seeing the actual paths here):
> 
> e2fsadm --size +20G LogicalVolumePath
> e2fsadm -- new size too large for "LogicalVolumePath"
> e2fsadm -- size of "LogicalVolumePath" would  be invalid
> 
> I thought to myself, 'Maybe I did this already.'  I was, afterall, just 
> starting me 1st cup of coffee.  Whenever I mount the filesystem and do a 
> df -h, it still reports 59G, which is what I started at.  
> 
> While this might still be a FS issue, I still can find nowhere else to 
> turn for assistance.

e2fsadm  does the logical volume resize as well as the filesystem stuff - so
effectively it is trying to do the same thing twice.

What you need to do now is simply the second part of what e2fsadm does and that
is the resize2fs

patrick

      reply	other threads:[~2002-07-10  8:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10  8:09 [linux-lvm] resizing logical volumes Ben Snyder
2002-07-10  8:32 ` Patrick Caulfield [this message]

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=20020710133238.GC822@tykepenguin.com \
    --to=caulfield@sistina.com \
    --cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.