From: Jonathan Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] how to add a mirror to an existing logical volume
Date: Wed, 04 Jan 2006 12:24:02 -0600 [thread overview]
Message-ID: <1136399042.20562.43.camel@hydrogen.msp.redhat.com> (raw)
In-Reply-To: <43BBA46E.20409@redhat.com>
When it's ready, it will be 'lvconvert'.
brassow
On Wed, 2006-01-04 at 18:33 +0800, dfang wrote:
> How to add a mirror to an existing logical volume?
> Use lvcreate or lvextend?
> Thanks.
>
> Fang,Dongyu
>
> _______________________________________________
> 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:[~2006-01-04 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 10:33 [linux-lvm] how to add a mirror to an existing logical volume dfang
2006-01-04 18:24 ` Jonathan Brassow [this message]
2006-01-05 2:18 ` Fang,Dongyu
2006-01-05 2:21 ` Fang,Dongyu
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=1136399042.20562.43.camel@hydrogen.msp.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 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).