From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How to fix inconsistent LV structs?
Date: Mon Oct 7 03:53:52 2002 [thread overview]
Message-ID: <20021007104201.A17176@sistina.com> (raw)
In-Reply-To: <3D9F6C62.1040004@raffael.ch>; from herzog@raffael.ch on Sun, Oct 06, 2002 at 12:49:06AM +0200
On Sun, Oct 06, 2002 at 12:49:06AM +0200, Raffael Herzog wrote:
> Hi,
>
> After a normal reboot I lost my volumes. I don't know, what
> exatly happended, but it looks like there was some problem
> with AVFS that caused umount not to work properly. I turned
> AVFS off now, but this doesn't get me my LVs back.
>
> pvdata shows me, that the logical volume structs 125 through
> 139 are inconsistent (there are no LVs there), at some later
> point, it segfaults. Debug output showed me, that there's
> some garbage in these logical volume structs.
Hmmm...
Sounds like a nasty overwrite but it is hard to tell because you
can't remmeber the exact details :(
>
> My basic idea is to just clear these structs and then use
> vgcfgrestore and/or the other recovery tools (which current-
> ly all fail with "pv_read(): read") to restore my LVs.
>
> But how do I clear these structs?
Presuming that the metadata backups are intact, you need to "pvcreate -ff"
the physical volumes and run vgcfgrestore on each of them.
"vgscan ; vgchange -ay" should get you back to business afterwards.
>
>
> TIA,
>
> Raffi
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-10-07 3:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 17:48 [linux-lvm] How to fix inconsistent LV structs? Raffael Herzog
2002-10-07 3:53 ` Heinz J . Mauelshagen [this message]
2002-10-07 4:29 ` Raffael Herzog
2002-10-07 5:35 ` Glenn Shannon
2002-10-07 6:32 ` Raffael Herzog
2002-10-07 6:43 ` Heinz J . Mauelshagen
2002-10-07 8:40 ` Raffael Herzog
2002-10-09 6:24 ` Heinz J . Mauelshagen
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=20021007104201.A17176@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