From: Alasdair G Kergon <agk@uk.sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] All LV have the same content after repair attempt
Date: Sun Mar 30 17:34:02 2003 [thread overview]
Message-ID: <20030331003341.A4025@uk.sistina.com> (raw)
In-Reply-To: <200303310028.27139.daniel.heemann@gmx.de>; from daniel.heemann@gmx.de on Sun, Mar 30, 2003 at 11:28:27PM +0100
On Sun, Mar 30, 2003 at 11:28:27PM +0100, Daniel Heemann wrote:
> b) the segment sections of the LV which used
> the broken hdd did not contain an entry like 'pvX' inside 'stripes' but
> 'Missing' was entered.
In future I want to replace 'Missing' with something that gives you
the PV's UUID, but some code restructuring is needed before I can make
that change.
I have also already added a command line switch '--removemissing' to
vgreduce intended to automate the LVM2 side of the process.
People need to read the vgreduce man page before using this option.
e.g. To run it with '--test' before running it for real.
> I also tried to use vgscan and vgchange from the LVM2.1.95.15 package but it
> fails to activate the vm,
> But I think that's due to missing kernel/module support for lvm2.
Correct. LVM2 needs device-mapper to activate the LVs.
Alasdair
--
agk@uk.sistina.com
next prev parent reply other threads:[~2003-03-30 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 16:29 [linux-lvm] All LV have the same content after repair attempt Daniel Heemann
2003-03-30 17:34 ` Alasdair G Kergon [this message]
2003-04-06 13:13 ` Daniel Heemann
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=20030331003341.A4025@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox