From: Markus Schiltknecht <markus@bluegap.ch>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Doubled PV
Date: Thu May 29 12:20:02 2003 [thread overview]
Message-ID: <1054232125.1862.8.camel@localhost> (raw)
In-Reply-To: <20030527130119.B8518@sistina.com>
On Tue, 2003-05-27 at 13:01, Heinz J . Mauelshagen wrote:
> Markus,
>
> what _exactly_ happened during the pvmove ?
Hard to reconstruct in detail, but as soon as the raid device has
'enough' failed devices, it doesn't respond to any request. It simply
isn't readable anymore.
> Would help to analyze any pvmove bug.
Don't think that's a bug in pvmove. Neigther in linux-softraid - just a
very bad accident. (If a bug at all, I would say it's an ATA bug...)
>
> Using LVM2 tools is a good idea.
>
> You'll have text metadata that way, would be able to hand-edit it removing
> the 10 LEs and vgcfgrestore the changed metadata back onto the PVs.
I could restore the single PV to a state, where it had no LEs on it.
(using vgcfgrestore from lvm 1). That way vgscan now finds just enough
LEs and I can activate the VG again.
Lucky me... ;-)
Thanks anyway.
Markus
prev parent reply other threads:[~2003-05-29 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 18:51 [linux-lvm] Doubled PV Markus Schiltknecht
2003-05-27 6:11 ` Heinz J . Mauelshagen
2003-05-29 12:20 ` Markus Schiltknecht [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=1054232125.1862.8.camel@localhost \
--to=markus@bluegap.ch \
--cc=linux-lvm@sistina.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