From: flavio-redhat@zipman.it
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvextend NEVER works but screws up
Date: Thu, 23 Aug 2012 16:21:33 +0200 [thread overview]
Message-ID: <50363C6D.7090104@zipman.it> (raw)
In-Reply-To: <CAGQjrKYZw27r=xgB2DaBtap-jQ1oi-7_Ydw=3z+2kw4s_03hAA@mail.gmail.com>
On 08/23/2012 01:14 PM, tariq wali wrote:
> I wanted to use the free 42.7 G and allocate it to /bin-logs so this is
> what I ran in order to extended
>
> # lvextend -L +42.7G -n /dev/vg0/logs
> Rounding up size to full physical extent 42.70 GB
> Extending logical volume logs to 142.70 GB
> Logical volume logs successfully resized
>
> #resize2fs /dev/vg0/logs ( and it gets screwed up here )
> resize2fs 1.39 (29-May-2006)
> *resize2fs: Filesystem has unsupported feature(s) while trying to open
> /dev/vg0/logs*
> *Couldn't find valid filesystem superblock.*
This problem seems to be with your filesystem tools, not with LVM. If I
were you I'd create a new LV, make a new filesystem, move all the files
on the new LV, mount it, remove the OLD LV and then extend the new LV.
--
Flavio Visentin
A computer is like an air conditioner,
it stops working when you open Windows
next prev parent reply other threads:[~2012-08-23 14:21 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
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 [this message]
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=50363C6D.7090104@zipman.it \
--to=flavio-redhat@zipman.it \
--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.