From: Greg Freemyer <greg.freemyer@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Re: invalid lv in extent map
Date: Tue, 6 Dec 2005 20:52:21 -0500 [thread overview]
Message-ID: <87f94c370512061752g3d948e01t15b17902a130da63@mail.gmail.com> (raw)
In-Reply-To: <87f94c370512061440s6b1b7ca0rffad7f53503309e4@mail.gmail.com>
Not sure how I caused the below, but after a reboot I was unable to
use my VG at all.
I wiped it out and rebuilt it. Hopefully it does not happen again.
Greg
On 12/6/05, Greg Freemyer <greg.freemyer@gmail.com> wrote:
> I have recently upgraded a test server from 2.4.x with LVM 1 to 2.6.13
> with LVM 2.
>
> I can mount my 3 LVs, but when I try to do basic lvm commands I get
> "invalid lv in extent map".
>
> # pvscan
> invalid lv in extent map
> Couldn't fill logical volume maps.
> invalid lv in extent map
> Couldn't fill logical volume maps.
> No matching physical volumes found
>
> # pvscan --version
> LVM version: 2.01.14 (2005-08-04)
> Library version: 1.01.04 (2005-08-02)
> Driver version: 4.4.0
>
> I did not run vgconvert manually, so I assume I still have LVM1 metadata.
>
> This is a test server, so none of the data in the LVs is important,
> but I hope to be upgrading my live file server soon, so I would like
> to figure out how to not lose any data.
>
> Thanks
> Greg
> --
> Greg Freemyer
> The Norcross Group
> Forensics for the 21st Century
>
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
prev parent reply other threads:[~2005-12-07 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 22:40 [linux-lvm] invalid lv in extent map Greg Freemyer
2005-12-07 1:52 ` Greg Freemyer [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=87f94c370512061752g3d948e01t15b17902a130da63@mail.gmail.com \
--to=greg.freemyer@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).