From: Alasdair G Kergon <agk@uk.sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] problem
Date: Wed Jan 8 15:45:02 2003 [thread overview]
Message-ID: <20030108214555.F28021@uk.sistina.com> (raw)
In-Reply-To: <1042057991.12153.0.camel@tux.its.uiowa.edu>; from daniel-wittenberg@uiowa.edu on Wed, Jan 08, 2003 at 02:33:11PM -0600
On Wed, Jan 08, 2003 at 02:33:11PM -0600, Daniel Wittenberg wrote:
> Other ideas?
Install the LVM2 utilities and perform the task with them?
"vgreduce --removemissing rootvg" will do exactly what you
want - but I haven't released it yet because I haven't finished
testing it with snapshots present etc.
For now, you run LVM2's vgcfgbackup (with -P), edit the
text file by hand to remove the PV and LV (easy to do), then
run vgcfgrestore to put the fixed metadata in the text file
back onto disk.
Then if you don't want to upgrade to LVM2 yet, you can
simply revert to using the LVM1 tools again, starting
by running LVM1's vgscan.
In circumstances like this, you don't need to change your
kernel in order to use the LVM2 tools. You can just set
"activation = 0" in the lvm.conf file and then they'll
only manipulate on-disk metadata and they won't try to
talk to device-mapper (the new kernel driver that LVM2 uses).
Alasdair
next prev parent reply other threads:[~2003-01-08 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 12:03 [linux-lvm] problem Daniel Wittenberg
2003-01-08 14:12 ` Steven Lembark
2003-01-08 14:32 ` Daniel Wittenberg
2003-01-08 15:45 ` Alasdair G Kergon [this message]
2003-01-08 16:24 ` Daniel Wittenberg
2003-01-08 16:29 ` Alasdair G Kergon
2003-01-08 16:34 ` Daniel Wittenberg
2003-01-08 16:54 ` Alasdair G Kergon
2003-01-08 17:09 ` Alasdair G Kergon
2003-01-08 17:14 ` Alasdair G Kergon
2003-01-09 14:26 ` Daniel Wittenberg
-- strict thread matches above, loose matches on Subject: below --
2002-12-26 1:34 [linux-lvm] Problem nellis
2002-12-26 7:17 ` Guido Guenther
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=20030108214555.F28021@uk.sistina.com \
--to=agk@uk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.