From: Alex Brett <alex@alexbrett.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Strange PV metadata issue
Date: Mon, 12 Jan 2009 09:32:36 +0000 [thread overview]
Message-ID: <496B0E34.8080404@alexbrett.net> (raw)
In-Reply-To: <496A8D96.9030209@alexbrett.net>
Alex Brett wrote:
> I assume what's happened (I'm no expert in lvm at all, so a lot of this
> is guessing) is that when I (stupidly) ran pvresize on the disk before
> rebooting, it somehow created this second metadata area, which the mkfs
> of my new LV overwrote in some way.
>
> Looking at the LVs that exist and their stripes, I'm fairly sure that
> this metadata area is *inside* the new 500G LV that I created, since
> that shows up as:
>
> segment1 {
> start_extent = 0
> extent_count = 128000 # 500 Gigabytes
>
> type = "striped"
> stripe_count = 1 # linear
>
> stripes = [
> "pv0", 128000
> ]
> }
> which obviously seems wrong to me!
>
> Can anybody suggest a way of dealing with this - can I manually edit the
> data on the partition to remove any reference to this second metadata
> area some how? Ideally I'd copy all the data off, and start from
> scratch, but unfortunately I don't have enough storage space to do that!
>
For anybody interested - I managed to fix this by forcing the pvcreate
with -ff, specifying only 1 metadata copy (not sure if I needed this bit
or not) and then a vgcfgrestore did the trick - all seems happy now :)
Alex
next prev parent reply other threads:[~2009-01-12 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 0:23 [linux-lvm] Strange PV metadata issue Alex Brett
2009-01-12 9:32 ` Alex Brett [this message]
2009-01-12 11:20 ` Bryn M. Reeves
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=496B0E34.8080404@alexbrett.net \
--to=alex@alexbrett.net \
--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.