From: Jonathan E Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] replacing a failling disk on a mirrred VG.
Date: Tue, 6 Feb 2007 07:40:03 -0600 [thread overview]
Message-ID: <abae97f2062bff4699caa277e2faea30@redhat.com> (raw)
In-Reply-To: <45C62BB0.6090004@free.fr>
This one should be pretty easy...
Effectively, you want to keep the primary mirror devices, so do:
lvconvert -m0 <vg/lv>
to down convert them to linear devices.
Then remove PV1 (vgreduce), add a new disk to your system, add it to
your vg (vgextend), and finally, up-convert the linear devices to
mirrors again:
lvconvert -m1 <vg/lv>
brassow
On Feb 4, 2007, at 12:53 PM, Georges Giralt wrote:
> Hi !
> I run A Fedora Core 6 box with
> lvm> version
> LVM version: 2.02.17 (2006-12-14)
> Library version: 1.02.13 (2006-11-28)
> Driver version: 4.10.0
> lvm>
> on a 2.6.19 kernel.
> My VG comprises 3PV onto which I've spread 4 mirrored LVs.
> PV 0 : LV1 mirror copy 0, LV2 mirror copy 0, lv3 mirror copy 0 and lv4
> mirror copy 0
> PV 1 : LV1 mirror copy 1, LV2 mirror log, LV3 mirror log and LV4
> mirror copy 1
> PV2 : LV1 mirror log, LV2 mirror copy 1 , LV3 mirror copy 1 and LV4
> mirror log.
> I plan to replace (Smart signals a future failure) the PV #1.
> Question : What is the best route to do this ? And is it feasible ?
> Thanks a lot in advance for your answer !
> --
> Ce message est constitu� d'au moins 50 % d'�lectrons recycl�s.
> S'il vous pla�t, aidez nous � conserver nos ressources,
> recyclez vos �lectrons !
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2007-02-06 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 18:53 [linux-lvm] replacing a failling disk on a mirrred VG Georges Giralt
2007-02-06 13:40 ` Jonathan E Brassow [this message]
2007-02-06 17:41 ` Steve Wray
2007-02-08 8:51 ` Jonathan E Brassow
2007-02-08 20:36 ` Georges Giralt
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=abae97f2062bff4699caa277e2faea30@redhat.com \
--to=jbrassow@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 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.