From: Phillip Susi <psusi@cfl.rr.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Jay <jrharris19@yahoo.com>
Subject: Re: [linux-lvm] LVM mirror questions
Date: Tue, 5 Oct 2010 11:40:46 -0400 [thread overview]
Message-ID: <4CAB46FE.9050309@cfl.rr.com> (raw)
In-Reply-To: <87363.97197.qm@web120701.mail.ne1.yahoo.com>
On 10/4/2010 7:55 PM, Jay wrote:
> the other disk and lvcovert. But it wouldn't work, saying I needed to
> add space on yet a third device for the log. Either that, or I could
> keep the mirror log in memory. Lvm would have to rebuild a 1TB mirror
> every time the system was rebooted if the log was left in memory. That
> doesn't sound efficient. So. Put the log on disk. I couldn't find
> an answer in man pages, but if the log is lost, then is the whole mirror
> lost ? That would mean to have the benefits of a mirror, the log would
> have to be at least as reliable as the mirror itself (or
> inconsequential).
>
> So, another mirror would have to be built of tiny size to hold the log,
> then lvconvert can be given something like -log disk /dev/vghuh/lvtiny,
> etc..
As you have noticed, LVM mirror support is basically broken or not fully
implemented yet. The mirror log SHOULD be stored on both legs of the
mirror in a block allocated automatically in the metadata area by lvm,
but isn't. If you want to mirror, you should do so using mdadm and then
use the md device as an lvm pv.
next prev parent reply other threads:[~2010-10-05 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 23:55 [linux-lvm] LVM mirror questions Jay
2010-10-05 8:02 ` Petr Rockai
2010-10-06 15:50 ` Jay
2010-10-06 16:37 ` Ray Morris
2010-10-06 17:23 ` Petr Rockai
2010-10-05 15:40 ` Phillip Susi [this message]
2010-10-06 15:26 ` Jay
2010-10-06 17:03 ` Stuart D. Gathman
2010-10-06 17:40 ` Petr Rockai
2010-10-06 18:57 ` Phillip Susi
2010-10-07 12:14 ` Petr Rockai
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=4CAB46FE.9050309@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=jrharris19@yahoo.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).