All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart D Gathman <stuart@bmsi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvextend NEVER works but screws up
Date: Fri, 24 Aug 2012 07:55:35 -0400	[thread overview]
Message-ID: <50376BB7.7010008@bmsi.com> (raw)
In-Reply-To: <CAGQjrKbLD0bwedMGQP58BzdyFsnACdXLiziHLbw=tStAhX4BsA@mail.gmail.com>

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

On 08/23/2012 11:18 AM, tariq wali wrote:
>  lvresize to extend an lvm ? how
>
> also I cant create a new lvm don't have that much space and the to 
> extend the new one and it would mean downtime . don't think it's an 
> issue with filesystem tools , lvm has NEVER been consistent in my case .
>
The resize2fs on RHEL5 does not support ext4.  Your error message is the 
one reported when you try to resize an ext4 filesystem with ext2/ext3 
tools.  You need to either install e4fsprogrs and use resize4fs (and 
e4fsck), or do the resize in the virtual machine you are apparently 
running a newer OS in.

[-- Attachment #2: Type: text/html, Size: 1473 bytes --]

  parent reply	other threads:[~2012-08-24 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 10:08 [linux-lvm] lvextend NEVER works but screws up tariq wali
2012-08-23 11:14 ` tariq wali
2012-08-23 14:10   ` Vic
2012-08-23 15:18     ` tariq wali
2012-08-23 15:23       ` Vic
2012-08-24  6:32       ` Jonathan Tripathy
2012-08-24 11:55       ` Stuart D Gathman [this message]
2012-08-27 11:46         ` tariq wali
2012-08-28  9:09           ` Zdenek Kabelac
     [not found]             ` <CAGQjrKajQYDc48i+FZhB5zUAJKHtMe4FqSgwx8Ed-z7wRuDVQQ@mail.gmail.com>
2012-10-04  6:32               ` tariq wali
2012-10-04 19:59                 ` Stuart D Gathman
2012-08-23 14:21   ` flavio-redhat
2012-08-23 16:08     ` Brassow Jonathan
2012-08-23 16:36   ` Bryn M. Reeves
2012-08-23 16:53     ` Stuart D Gathman

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=50376BB7.7010008@bmsi.com \
    --to=stuart@bmsi.com \
    --cc=linux-lvm@redhat.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.