From: Barnaby Claydon <bclaydon@volved.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Misleading documentation
Date: Wed, 20 Sep 2006 15:45:47 -0400 [thread overview]
Message-ID: <45119A6B.6090508@volved.com> (raw)
In-Reply-To: <1158751643.12030.46.camel@bounty.rider.geekspirit.net>
Fabien Jakimowicz wrote:
> On Wed, 2006-09-20 at 03:22 +0000, Mark Krenz wrote:
>
>> Personally I like it when documentation is kept simple and uses simple
>> examples. There is nothing worse than when you are trying to learn
>> something and it tells you how to how to intantiate a variable, and then
>> it immediately goes on to show you how to make some complicated reference
>> to it using some code.
>>
>> I agree with you though, its probably a good idea to steer newcomers
>> in the right direction on disk management and a few notes about doing
>> LVM ontop of RAID being a good idea couldn't hurt. This is especially
>> so since I've heard three mentions of people using LVM on a server
>> without doing RAID this week alone. :-/
>>
> We should add something in faq page
> ( http://tldp.org/HOWTO/LVM-HOWTO/lvm2faq.html ), like "i've lost one of
> my hard drive and i can't mount my lv, did i lost everything ?" followed
> by a quick explanation : lvm is NOT faulty tolerant like raid1/5, if you
> lose a PV, you lose every LV which was (even partially) on on it.
>
<snip>
Not to nit-pick, but when one of my multi-PV LVs experienced a single PV
failure, I did NOT lose all the data on the LV. The VG was using linear
spanning, so using the --partial parameter with read-only file-system
mounting (XFS in my case) I recovered all the data from the LV that
wasn't physically spanned onto the failed PV.
If this was some sort of miracle and shouldn't have worked, well I
suppose I'll count my blessings but it seemed perfectly reasonable at
the time.
:)
-Barnaby
next prev parent reply other threads:[~2006-09-20 20:46 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 ` Barnaby Claydon [this message]
2006-09-20 10:50 ` [linux-lvm] Misleading documentation Morten Torstensen
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=45119A6B.6090508@volved.com \
--to=bclaydon@volved.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 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.