From: Dominique Quatravaux <dom@idealx.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: pierre.machard@idealx.com, Benoit Picaud <benoit@idealx.com>,
'Mathias BROSSARD' <mbrossard@idealx.com>
Subject: Re: [linux-lvm] [BUG] Spaces in LVM1 LV names => *deep trouble* when converting to LVM2
Date: Thu, 11 May 2006 09:55:03 +0200 [thread overview]
Message-ID: <4462EDD7.8060409@idealx.com> (raw)
In-Reply-To: <20060510204038.GX16180@agk.surrey.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alasdair G Kergon wrote:
>
> I should add that what you should do is extract the metadata you've
> retrieved off disk directly into a file, fix it in the file
> (differences in whitespace & comments don't matter) then use
> vgcfgrestore -f.
I tried that and it works - strange, I tried vgcfgrestore yesterday to
no avail... But then I was using Ubuntu 5.10's lvm2 package as a
rescue so apparently it's a different (and solved) issue. Thanks!
Knowing this, and still for the record: after any LVM operation it
seems wise to try a vgchange -a y *before* rebooting to see if
everything went well. Reverting a pickled LVM situation is much easier
with the original toolset handy (same LVM binary and metadata backups
in /etc/lvm/) than using a rescue CD!
I wrote, and you replied:
>> * there should be a mechanism for dealing with corrupt LVM
>> metadata, at the minimum a global command-line switch to
>> temporarily disable checksum verifications.
>
> Nope.
>
I seem to have pushed your button, apologies for doing so. I was
trying to be humorous, not disparaging: *of course* I concur that
checksums are a good idea! I guess it means that humor is too slippery
for us non-native speakers, oh well...
- --
Dominique QUATRAVAUX Ing�nieur senior
01 44 42 00 08 IDEALX
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEYu3XMJAKAU3mjcsRAugqAKC2KK88j/+w30xd6pxcn/5Juu7tuACdExXi
R2b4HLcvmPmWHl+uxhbvGi0=
=tWX0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-11 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 20:26 [linux-lvm] [BUG] Spaces in LVM1 LV names => *deep trouble* when converting to LVM2 Dominique Quatravaux
2006-05-10 20:36 ` Alasdair G Kergon
2006-05-10 20:40 ` Alasdair G Kergon
2006-05-11 7:55 ` Dominique Quatravaux [this message]
2006-05-10 21:20 ` [Evms-devel] " Kevin Corry
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=4462EDD7.8060409@idealx.com \
--to=dom@idealx.com \
--cc=benoit@idealx.com \
--cc=linux-lvm@redhat.com \
--cc=mbrossard@idealx.com \
--cc=pierre.machard@idealx.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).