From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vg recovery after PV failure
Date: Wed Apr 10 09:05:02 2002 [thread overview]
Message-ID: <20020410160541.A967@sistina.com> (raw)
In-Reply-To: <1018291425.21592.7.camel@snifter>; from eamonn.hamilton@saic.com on Mon, Apr 08, 2002 at 07:43:44PM +0100
Eamonn,
in case "a bit odd" means a HW flaw, you need to vgcfgrestore the LVM metadata
back onto a sane device. You can even "vgcfgrestore -i" to a disk with
different size, bacause you loose the data on the old flaky disk anyway
(assuming it is completely inaccessable) :-(
If your friend had all LVs striped onto both PVs, data is lost anyway.
Hint: backups are your friends friends.
On Mon, Apr 08, 2002 at 07:43:44PM +0100, Eamonn Hamilton wrote:
>
>
> Hi Folks.
>
> I'm attempting to recover a VG on a friends system after one of the PVs
> started acting a bit odd. The VG appears to say that it has no PVs
> associated with it, and a vgscan only finds the second PV on the disk. A
> pvdisplay, however, show both physical volumes have what appears to be
> the correct information and extents.
>
> I'm basically wondering how do I get these two physical volumes
> associated again, and is there any way to determine how they were put
> topgether, i.e. were they striped? Also, is there any way to get the
> information off the non-dodgy disk ( it's ext3, btw ).
>
> Cheers,
>
> Eamonn
>
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2002-04-10 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 13:45 [linux-lvm] vg recovery after PV failure Eamonn Hamilton
2002-04-10 9:05 ` Heinz J . Mauelshagen [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=20020410160541.A967@sistina.com \
--to=mauelshagen@sistina.com \
--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