From: David Vidal Rodriguez <vidalrod@informatik.tu-muenchen.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problem with UUID, vgscan, vgcfgrestore
Date: Wed, 25 Apr 2001 13:51:03 +0200 [thread overview]
Message-ID: <3AE6BA27.1FC18A3C@in.tum.de> (raw)
In-Reply-To: 01040307345000.00915@darkvader
Oh yes, this procedure has helped me too! I had the same problem and now I can
use my VG with no single byte being lost. But from now on I'll start making
backups of my data... :) Thanks!
> > OK, I have figured out why vgcfgrestore doesn't work properly with broken
> > UUIDs. It is because vgcfgrestore only restores the backup VGDA data to
> > each disk separately. This means it is not possible to have consistent
> > UUIDs generated for all PVs in a VG when vgcfgrestore is run.
> >
> > You can try the following (experimental) procedure to fix the UUIDs:
> >
> > Check each PV with "pvdata -PP /dev/hdX" to ensure it has a valid
> > UUID assigned. Also get the PV numbers (starting with 1) for each of
> > the PVs. Finally, check the pv_uuidlist_on_disk.base for each PV.
> > It will normally be 6144, but it does not have to be.
> >
> > for each PV (in PV# order)
> > dd if=/dev/hdX bs=1 skip=44 count=128 >> /tmp/uuids
> >
> > This should create a file /tmp/uuids which has all of the PV UUIDs in it.
> > Make sure there are as many UUIDs in the file ("od -a /tmp/uuids" is good)
> > as you have PVs (8 in your case).
> >
> > Now, we want to write the UUID list back to the PVs so vgscan is happy:
> >
> > for each PV (in any order)
> > dd if=/tmp/uuids of=/dev/hdX bs=1 seek=<pv_uuidlist_on_disk.base for
> > hdX>
>
> Unfortunately this doesn't work. I get on of=/dev/hda2 an invalid argument.
> Can you write to a partition with dd ? Or has it to be a disk such as
> /dev/hda ?
>
> >
> > example:
> > dd if=/tmp/uuids of=/dev/hda2 bs=1 seek=6144
> >
> > Now vgscan should be able to detect all of the disks and work properly.
> >
> > Cheers, Andreas
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
------------------------------------------------------------------------
David Vidal R. (vidalrod@in.tum.de)
http://dvr.ismad.com
"Ein Computer ohne Windows ist wie ein Fisch ohne Fahrrad."
next prev parent reply other threads:[~2001-04-25 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 5:43 [linux-lvm] Problem with UUID, vgscan, vgcfgrestore Diederick van Dijk
2001-04-02 21:00 ` Andreas Dilger
2001-04-03 5:34 ` Diederick van Dijk
2001-04-03 6:23 ` Andreas Dilger
2001-04-03 7:51 ` Diederick van Dijk
2001-04-03 20:43 ` Diederick van Dijk
2001-04-03 21:36 ` Andreas Dilger
2001-04-03 22:15 ` Diederick van Dijk
2001-04-03 22:30 ` Andreas Dilger
2001-04-25 11:51 ` David Vidal Rodriguez [this message]
2001-04-25 15:49 ` Heinz J. Mauelshagen
2001-04-25 14:03 ` David Vidal Rodriguez
2001-04-25 16:26 ` Andreas Dilger
2001-04-27 10:47 ` Heinz J. Mauelshagen
2001-04-30 18:16 ` Andreas Dilger
2001-05-02 12: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=3AE6BA27.1FC18A3C@in.tum.de \
--to=vidalrod@informatik.tu-muenchen.de \
--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;
as well as URLs for NNTP newsgroup(s).