From: Georges Giralt <georges.giralt@free.fr>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Mirrored LV
Date: Tue, 16 Sep 2008 21:56:01 +0200 [thread overview]
Message-ID: <48D00F51.5090305@free.fr> (raw)
In-Reply-To: <1221592827.6037.57.camel@localhost>
Koen Vermeer a �crit :
> 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
Koen,
I confirm that you have to use 3 disks to mirror a VG with the actual
version of software.
At home, having enough disk, I use 3 disks to get my VG/LV mirrored and
it works flawlessly since a couple of years.
At work, we have mirrored the PV using 2 devices and the software RAID
(md) and build the VG/LV on top of that. It runs flawlessly for 4 years
I think (have to check the exact installation date...) So choice is yours...
HAve a nice day.
P.S. At home, I do not use the whole PV for my LV.
Each PV is split in two dissymitrical parts : a small 100 M partition
and the rest of the device. The small partition is used for a software
RAID (md) to hold the /boot. The rest of the disk as a regular PV used
to build the mirrored VG/LV. This way, if one disk breaks I still can
boot onto the remaining one. Of course, it is a manual boot but easier
compared to searching a useable rescue CD and the correct kernel
version. Think about it.
--
If the only tool you have is a hammer, you tend to see every problem as
a nail.
Abraham Maslow
next prev parent reply other threads:[~2008-09-16 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 19:20 [linux-lvm] Mirrored LV Koen Vermeer
2008-09-16 19:56 ` Georges Giralt [this message]
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=48D00F51.5090305@free.fr \
--to=georges.giralt@free.fr \
--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.