From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvreduce
Date: Tue, 23 Oct 2007 02:08:20 +0100 [thread overview]
Message-ID: <20071023010820.GU10006@agk.fab.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0710222032460.11239-100000@bmsred.bmsi.com>
On Mon, Oct 22, 2007 at 08:36:26PM -0400, Stuart D. Gathman wrote:
> On Mon, 22 Oct 2007, Humble Chirammal wrote:
> > One of the customer ran "lvreduce" command without reducing the
> > filesystem (resize2fs ). After the system was rebooted got this error.
> > <<snip>>
> > The filesystem size (according to the superblock) is 19922944 blocks
> > The physical size of the device is 13369344 blocks
> > Either the superblock or the partition table is likely to be corrupt!
> > <<snip>>
> > Is there any way for data recovery???
> Stop them from doing anymore LVM operations until recovery.
> If nothing else has been done, undo the lvreduce with vgrestore.
> LVM keeps backup versions of the metadata (/etc/lvm/archive on my
> system). I'll let the experts provide the exact syntax. I haven't
> had to do it yet :-)
> If they have used the freed extents (lvextend or lvcreate or ...),
> then they are hosed.
Indeed - as long as they made no other changes, 'vgcfgrestore' will undo the
lvreduce operation. You can use '-ll' to check.
If they're using X, suggest trying the GUI (packages system-config-lvm)
interface to carry out resizing.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2007-10-23 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 4:41 [linux-lvm] lvreduce Humble Chirammal
2007-10-22 6:14 ` Itamar Reis Peixoto
2007-10-23 0:36 ` Stuart D. Gathman
2007-10-23 1:08 ` Alasdair G Kergon [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-26 11:37 Bradley M Alexander
2003-06-27 4:41 ` Heinz J . Mauelshagen
2003-06-27 6:28 ` Bradley Alexander
2001-09-18 9:09 G'abor Luk'acs
2001-09-18 10:20 ` Heinz J . Mauelshagen
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=20071023010820.GU10006@agk.fab.redhat.com \
--to=agk@redhat.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).