From: "Matt P" <slarty.tj@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Mirror between different SAN fabrics
Date: Wed, 27 Dec 2006 14:47:51 -0600 [thread overview]
Message-ID: <859a78260612271247m7b14c247n7f420c7ebea5b906@mail.gmail.com> (raw)
In-Reply-To: <4339128.1167221745260.JavaMail.mailer@post.ch>
I guess I should have tested the functionality out before I made the
comment. It seems the ability to add a mirror after the fact is still
not available (in lvconvert or otherwise). I'm sure someone will
correct me if I wrong on that.
I did figure out a crazy way you could do it, but it's messy, even
with small number of PVs. It would impact performance and is probably
not feasible in reality.
I think the proper way would be to use mdadm. Setup software RAID1
prior to getting LVM involved...
On 12/27/06, mathias.herzog@postfinance.ch
<mathias.herzog@postfinance.ch> wrote:
>
> > From: linux-lvm-bounces@redhat.com
> > [mailto:linux-lvm-bounces@redhat.com] On Behalf Of Matt P
>
> > I can't think of any Volume Manager that would let you mirror
> > disks from 2 separate VGs...
> Maybe not from 2 separate VGs but they add an additional level to group
> PVs together. With HP-UX you can use "lvcreate -m -s g" to use different
> PV-groups for the mirror. With Tru64 as far as I know you can use a Plex
> to create a PV-group (should be similar with Veritas)
>
> > But other than that I wouldn't see why you couldn't use 2
> > different fabrics, they're just disks to LVM... If you're
> > having trouble managing 200+ PVs, just build the LV first
> > using only disks from 1 fabric, then make the second fabric
> > available/visible, and add a mirror using only those disks...
> > I think that would work...
> That's an idea, but when I'm adding 4 more disks (eg. disk1 and disk2
> from fabric1, disk3 and disk4 from fabric2), how can I tell LVM to
> mirror Disk1,2 to Disk3,4 and not to mirror Disk1 to Disk2?
>
> Regards Mathias
>
> Sicherheitshinweis:
> Dieses E-Mail von PostFinance ist signiert. Weitere Informationen finden Sie unter:
> https://www.postfinance.ch/e-signature.
> Geben Sie Ihre Sicherheitselemente niemals Dritten bekannt.
>
> _______________________________________________
> 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-12-27 20:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 14:01 [linux-lvm] Mirror between different SAN fabrics mathias.herzog
2006-12-22 15:51 ` Matt P
2006-12-27 12:15 ` mathias.herzog
2006-12-27 20:47 ` Matt P [this message]
2006-12-28 8:12 ` mathias.herzog
2006-12-28 8:49 ` Christian.Rohrmeier
2006-12-28 10:13 ` mathias.herzog
2006-12-28 10:55 ` Christian.Rohrmeier
2006-12-28 11:09 ` Graham Wood
2006-12-28 11:31 ` Christian.Rohrmeier
2006-12-28 11:42 ` Graham Wood
2006-12-28 11:52 ` mathias.herzog
2006-12-28 18:19 ` Ty! Boyack
2006-12-28 19:30 ` Matt P
2006-12-28 22:02 ` Ty! Boyack
2006-12-28 23:24 ` Matt P
2007-01-03 16:30 ` mathias.herzog
2007-01-05 12:27 ` mathias.herzog
2006-12-29 13:10 ` [linux-lvm] Filter the Swap Partition berthiaume_wayne
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=859a78260612271247m7b14c247n7f420c7ebea5b906@mail.gmail.com \
--to=slarty.tj@gmail.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).