From: malahal@us.ibm.com
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Mirrored LVs
Date: Fri, 23 Oct 2009 10:29:14 -0700 [thread overview]
Message-ID: <20091023172914.GA12748@us.ibm.com> (raw)
In-Reply-To: <4AE1B9FB.504@mortent.org>
Morten Torstensen [morten@mortent.org] wrote:
> Why cannot the mirrorlog be stored persistently in one or more LEs in
> the LV? Why the need for a seperate PV for this?
For better redundancy...
> Since most servers I work with have two disks for the system, this force
> me to use md for mirroring, adding unneeded complexity for a simple mirror.
Use "--alloc anywhere" to place the log LV on one of them when you
create your mirror.
next prev parent reply other threads:[~2009-10-23 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 14:13 [linux-lvm] Mirrored LVs Morten Torstensen
2009-10-23 17:29 ` malahal [this message]
2009-10-23 18:28 ` Morten Torstensen
2009-10-23 19:02 ` malahal
2009-10-23 19:15 ` Alasdair G Kergon
2009-10-23 19:41 ` Morten Torstensen
2009-10-23 18:40 ` brem belguebli
2009-10-23 19:15 ` malahal
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=20091023172914.GA12748@us.ibm.com \
--to=malahal@us.ibm.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).