From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: tariq wali <ganaiwali@gmail.com>
Subject: Re: [linux-lvm] lvextend NEVER works but screws up
Date: Thu, 23 Aug 2012 17:36:15 +0100 [thread overview]
Message-ID: <50365BFF.503@redhat.com> (raw)
In-Reply-To: <CAGQjrKYZw27r=xgB2DaBtap-jQ1oi-7_Ydw=3z+2kw4s_03hAA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/23/2012 12:14 PM, tariq wali wrote:
> # 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
Afaik the -n is not necessary here - it's only meaningful with resize
operations if the --resizefs option is also given (so it only calls
fsadm resize and not fsadm check).
> #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 is the problem. You appear to be using a version of e2fsprogs
that is older than the version used to create the file system in the
first place. In this case they will give up and refuse to do anything
rather than potentially damage a file system that has unknown features
enabled.
> lvm version LVM version: 2.02.88(2)-RHEL5 (2012-01-20) Library
> version: 1.02.67-RHEL5 (2011-10-14) Driver version: 4.11.6
Can you post the version of e2fsprogs you have installed and also the
output of "dumpe2fs -h /dev/vg0/logs"?
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlA2W/8ACgkQ6YSQoMYUY95y8ACgwTykP1Z/izonns5vvM5dm8nf
/LMAn3zw8RYpabEJ38k5s9Lg5Xt7zlkr
=ipyA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-08-23 16:36 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
2012-08-23 16:08 ` Brassow Jonathan
2012-08-23 16:36 ` Bryn M. Reeves [this message]
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=50365BFF.503@redhat.com \
--to=bmr@redhat.com \
--cc=ganaiwali@gmail.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 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).