From: Navindra Umanee <navindra@cs.mcgill.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] setting VG UUID
Date: Wed Jan 7 08:26:01 2004 [thread overview]
Message-ID: <20040107092415.A28215@cs.mcgill.ca> (raw)
In-Reply-To: <20040107065801.A27995@cs.mcgill.ca>; from Navindra Umanee on Wed, Jan 07, 2004 at 06:58:01AM -0500
> After figuring out that my all my PVs were lacking UUIDs, I used this
> hack from Heinz to correct the situation:
>
> http://lists.sistina.com/pipermail/linux-lvm/2002-January/010521.html
>
> (Alasdair also kindly provided a patch to handle the situation in LVM2.)
>
> Now my VG itself is still lacking a UUID and this causes problems such
> as vgcfgrestore refusing to continue. Is there any way I can update
> my VG UUID?
For the record, I'm absolutely crazy, but I fixed this by doing:
echo "deadbeefdeadbeefdeadbeefdeadbeef"|dd of=/dev/hda6 obs=1 seek=4096 count=32
echo "deadbeefdeadbeefdeadbeefdeadbeef"|dd of=/dev/hda7 obs=1 seek=4096 count=32
echo "deadbeefdeadbeefdeadbeefdeadbeef"|dd of=/dev/hda8 obs=1 seek=4096 count=32
echo "deadbeefdeadbeefdeadbeefdeadbeef"|dd of=/dev/hda9 obs=1 seek=4096 count=32
So much for universal uniqueness... but now finally LVM2 is happy to
accept my LVM1 partitions! Woohoo!!
For the record, I created my LVM1 partitions with Linux Mandrake 9.2.
So I anticipate other people will be having this kind of fun. :-)
One inconvenience I still seem to have is that /dev/bytepool/ is now
filled with symlinks and when I boot back to Linux 2.4 with LVM1 (no
device-mapper), it fails to mount the partitions because of this.
Cleaning /dev/bytepool/ and rebooting seems to fix this.
Should "vgchange -a n" maybe clean up these symlinks?
Cheers,
Navin.
next prev parent reply other threads:[~2004-01-07 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 6:00 [linux-lvm] setting VG UUID Navindra Umanee
2004-01-07 8:26 ` Navindra Umanee [this message]
2004-01-08 16:27 ` Alasdair G Kergon
2004-01-08 16:35 ` Navindra Umanee
2004-03-12 17:17 ` Dan Merillat
2004-01-22 16:50 ` Luca Berra
2004-01-22 20:53 ` Navindra Umanee
2004-01-23 2:27 ` Luca Berra
2004-01-23 8:37 ` Alasdair G Kergon
2004-01-23 14:33 ` Luca Berra
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=20040107092415.A28215@cs.mcgill.ca \
--to=navindra@cs.mcgill.ca \
--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