linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Morten Torstensen <morten@mortent.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Misleading documentation
Date: Wed, 20 Sep 2006 12:50:02 +0200	[thread overview]
Message-ID: <45111CDA.6080406@mortent.org> (raw)
In-Reply-To: <4B875923-CB76-4792-837B-EDA3B9E53756@slamb.org>

Scott Lamb wrote:
> This is my biggest beef with LVM - why doesn't *any* of the 
> documentation point this out? There are very few good reasons to use LVM 
> without RAID, and "ignorance" certainly isn't among them. I don't see 
> any mention of RAID or disk failures in the manual pages or in the HOWTO.

Mirroring should be dealt with in LVM itself, by mapping more PEs on physical 
seperate PVs to each LE. From the little information I've seen about the new LVM 
mirroring, it seems that the mirrors are defined on LV level instead of LE/PE. 
But after some JFGI sessions nothing really enlightening has shown up.

-- 

//Morten Torstensen
//Email: morten@mortent.org
//IM: Cartoon@jabber.no morten.torstensen@gmail.com

And if it turns out that there is a God, I don't believe that he is evil.
The worst that can be said is that he's an underachiever.

  parent reply	other threads:[~2006-09-20 10:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 18:10 [linux-lvm] HDD Failure Nick
2006-09-18 19:08 ` Mitch Miller
2006-09-18 19:13   ` Nick
2006-09-18 19:23     ` Fabien Jakimowicz
2006-09-18 19:34       ` Nick
2006-09-18 19:37         ` Mark Krenz
2006-09-19 22:40           ` [linux-lvm] Misleading documentation (was: HDD Failure) Scott Lamb
2006-09-20  0:35             ` Fabien Jakimowicz
2006-09-20  3:22             ` Mark Krenz
2006-09-20 11:27               ` Fabien Jakimowicz
2006-09-20 19:45                 ` [linux-lvm] Misleading documentation Barnaby Claydon
2006-09-20 10:50             ` Morten Torstensen [this message]
2006-09-20 11:40               ` Heinz Mauelshagen
2006-09-20 12:41                 ` Les Mikesell
2006-09-21  9:42                   ` Heinz Mauelshagen
2006-09-21 12:52                     ` Les Mikesell
2006-09-20 13:22             ` [linux-lvm] Misleading documentation (was: HDD Failure) Tobias Bluhm
2006-09-20 23:21               ` Scott Lamb
2006-09-18 19:42         ` [linux-lvm] HDD Failure Fabien Jakimowicz
2006-09-18 19:52           ` Nick
2006-09-18 19:57             ` Fabien Jakimowicz
2006-09-19 21:53               ` [linux-lvm] LVM on RAID Alexander Lazarevich
2006-09-19 22:03                 ` Roger Lucas
2006-09-24 17:19                   ` Nix
2006-09-19 22:04                 ` Mark Krenz
2006-09-19 22:11                 ` Michael Loftis
2006-09-20  0:30                 ` Fabien Jakimowicz
2006-09-20 13:55                 ` Matthew B. Brookover
2006-09-20 14:01                   ` Michael T. Babcock
2006-09-20 14:48                   ` Alexander Lazarevich
2006-09-20 15:57                     ` Fabien Jakimowicz
2006-09-21  3:19                     ` Andrew Boyko
2006-09-20 17:24                   ` Mark H. Wood

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=45111CDA.6080406@mortent.org \
    --to=morten@mortent.org \
    --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).