From: Koen Vermeer <koen@vermeer.tv>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Mirrored LV
Date: Tue, 16 Sep 2008 21:20:27 +0200 [thread overview]
Message-ID: <1221592827.6037.57.camel@localhost> (raw)
Hi,
I was thinking of using a mirrored LV as a easier to use alternative to
a RAID1 PV (with matching VG and LV). I tried to find the information I
need on how this works and how to set it up, but so far, I failed.
First, am I right in trying to use LVM in this way? I have two disks,
and I just want to mirror some LVs.
Second, I am confused by the apparent need to have this log stored on
another device. Actually, this doesn't seem true in two ways: There's
the option of having the log in memory and then the documentation only
says that the log is 'usually on a separate device'. Does that mean that
using a mirrored LV makes no sense on a system with two disks? Or should
I just keep the log in memory in this case? Or can I use another PV on
one of the disks? Should this be mirrored as well? What happens if I
loose that data?
From what I found when searching for answers, it seems that I'm not the
only one that's confused... But maybe my searching skills are just
lacking. Anyway, I appreciate any help and insights!
Best,
Koen
next reply other threads:[~2008-09-16 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 19:20 Koen Vermeer [this message]
2008-09-16 19:56 ` [linux-lvm] Mirrored LV Georges Giralt
2008-09-16 20:20 ` Koen Vermeer
2008-09-16 20:42 ` malahal
2008-09-16 21:12 ` Koen Vermeer
2008-09-16 21:57 ` malahal
2008-09-17 7:36 ` Koen Vermeer
2008-09-19 15:06 ` Koen Vermeer
2008-09-19 17:31 ` malahal
2008-09-19 22:01 ` Koen Vermeer
2008-09-20 3:39 ` Jonathan Brassow
2008-09-22 21:21 ` malahal
2008-09-23 8:41 ` Koen Vermeer
2008-09-16 23:01 ` Larry Dickson
2008-09-17 1:22 ` 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=1221592827.6037.57.camel@localhost \
--to=koen@vermeer.tv \
--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.