From: Tom Wizetek <tom@wizetek.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Removing a failed PV from VG/LV
Date: Wed, 8 Sep 2010 01:04:17 -0400 [thread overview]
Message-ID: <AANLkTim2mRkOGRuuMgbNtC8WJqppuFUdSLf7puUHy5ug@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=2K2=V3Pj8aMx7uB_+Fqn12ZWa1EteKQhH=uAu@mail.gmail.com>
Please disregard my previous inquiry about pvcreate on loop. I got it
to work by doing 'losetup /dev/loop0 disk-image'. That was off-topic
anyway.
To state what information I'm looking for in a more concise form:
How to go about restoring a VG without having to physically replace a
failed PV? Is it possible to create a "fake" PV, restore LVM metadata,
fsck the filesystem and finally remove the PV?
--
TW
prev parent reply other threads:[~2010-09-08 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 5:56 [linux-lvm] Removing a failed PV from VG/LV Tom Wizetek
2010-09-02 10:24 ` Bryn M. Reeves
2010-09-02 20:43 ` Tom Wizetek
2010-09-08 5:04 ` Tom Wizetek [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=AANLkTim2mRkOGRuuMgbNtC8WJqppuFUdSLf7puUHy5ug@mail.gmail.com \
--to=tom@wizetek.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).