From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM ate my data!
Date: Mon Feb 25 12:28:02 2002 [thread overview]
Message-ID: <20020225192811.A9674@sistina.com> (raw)
In-Reply-To: <E16fPYj-0006mn-00@cpca7.uea.ac.uk>; from lvm-mail@wbh.org on Mon, Feb 25, 2002 at 06:09:09PM +0000
On Mon, Feb 25, 2002 at 06:09:09PM +0000, lvm-mail@wbh.org wrote:
> Hiya.
> I've just upgraded my kernel, and on booting my LVM setup isn't
> recognised. Going back to the old kernel, it still isn't.
> Running vgscan gives:
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found inactive volume group "pvg"
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get data of volume group "pvg" from physical volume(s)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating "/etc/lvmtab" and "/etc/lvmtab.d"
>
In case *all* your PVs making up your VG are accessable, your LVM metadata
looks toasted.
> OK, create a new vg and import?
No.
You need to "pvcreate -ff" your PVs and vgcfgrestore a metadata backup
to all of them.
Before doing so, you can save your actual metadata for recovery in case
something goes badly wrong with:
for d in /dev/hda[34]
do
dd if=$d of=$(basename $d).vgda bs=1k count=1k
done
So, assuming /dev/hda[34] are all your PVs which belonged to the missing VG
(otherwise add those), figure out the recent metadata backup in /etc/lvmconf.
Say /etc/lvmconf/VG.conf would be the one.
Then run:
pvcreate -yff /dev/hda[34]
vgcfgrestore -n YourVGName /dev/hda3
vgcfgrestore -n YourVGName /dev/hda4
vgscan
vgchange -ay
> vgcreate gives:
> vgcreate -- ERROR: "/etc/lvmtab" doesn't exist; please run vgscan
> and pvscan gives:
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- inactive PV "/dev/hda3" is associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/hda4" is associated to an unknown VG (run vgscan)
> pvscan -- total: 2 [16.88 GB] / in use: 2 [16.88 GB] / in no VG: 0 [0]
>
> Where do I go from here - vgcfgrestore? uuid_fixer? Even something really smelly!
Please upgrade to LVM 1.0.3 and do the pvcreate + vgcfgrestore above.
> Thanks,
> Bill
> (Sorry if this comes over a bit garbled, I'm posting using lynx, 'coz
> pine's somewhere on /dev/hda4 ...)
>
>
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-02-25 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 12:09 [linux-lvm] LVM ate my data! lvm-mail
2002-02-25 12:28 ` Heinz J . Mauelshagen [this message]
2002-02-25 13:14 ` wbh
2002-02-26 4:47 ` Heinz J . Mauelshagen
2002-02-25 14:18 ` wbh
2002-02-26 4:45 ` 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=20020225192811.A9674@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