From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Big question ...
Date: Wed, 22 Nov 2006 23:10:04 +0000 [thread overview]
Message-ID: <4564D8CC.7050705@redhat.com> (raw)
In-Reply-To: <200611222343.16722.martial.paupe@nagra.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martial Paupe wrote:
> Hello Bryn,
>
> On Wednesday 22 November 2006 23:29, Bryn M. Reeves wrote:
> I think that you speak about LVM2. I use RHES 3.5 and the version of lvm are
> lvm-1.0.8-14.
>
Yes, I was referring to LVM2. LVM1 doesn't have the --removemissing flag
to vgreduce.
By default LVM1 should make a backup of the volume group metadata before
the vgextend command adds a new PV- it's worth checking /etc/lvmconf to
see if you can restore the old metadata.
Use vgcfgrestore -f <file> -n <vgname> -ll to see the physical & logical
volumes in the backups and restore from the last good one (only the
metadata is restored - data in the LVs remains unchanged).
See the man page for vgcfgbackup/vgcfgrestore for more details.
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFZNjM6YSQoMYUY94RAl+BAJ9Uk4x6vBPyd3t/yNRn5dsKF1+DSQCg1n4r
LV8bL4p55bumwzSbmQXunok=
=RPre
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-11-22 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 22:04 [linux-lvm] Big question Martial Paupe
2006-11-22 22:29 ` Bryn M. Reeves
2006-11-22 22:43 ` Martial Paupe
2006-11-22 23:10 ` Bryn M. Reeves [this message]
2006-11-22 23:48 ` Martial Paupe
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=4564D8CC.7050705@redhat.com \
--to=breeves@redhat.com \
--cc=linux-lvm@redhat.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