linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Henrik Holst <henrik.holst@idgmail.se>
Cc: Bodo Thiesen <bothie@gmx.de>,
	linux-raid mailing list <linux-raid@vger.kernel.org>,
	Ken Walker <ken.walker@manchester.ac.uk>
Subject: Re: why partition arrays?
Date: Tue, 24 Oct 2006 19:31:12 -0400	[thread overview]
Message-ID: <453EA240.7000407@tmr.com> (raw)
In-Reply-To: <453A232E.8050401@idgmail.se>

Henrik Holst wrote:

>Bodo Thiesen wrote:
>  
>
>>Ken Walker <ken.walker@manchester.ac.uk> wrote:
>>
>>    
>>
>>>Is LVM stable, or can it cause more problems than separate raids on a array.
>>>      
>>>
>
>[description of street smart raid setup]
>
>(The same function could probably be achieved with logical partitions
>and ordinary software raid levels.)
>
>  
>
>>So, now decide for your own, if you consider LVM stable - I would ;)
>>
>>Regards, Bodo
>>    
>>
>
>Have you lost any disc (i.e. "physical volumes") since February? Or lost
>the meta-data?
>
>I would not recommend anyone to use LVM if they are less than experts on
>Linux systems. Setting up a LVM system is easy: administrating and
>salvaging the same, was much more work. (I used it ~3 years ago)
>
My read on LVM is that (a) it's one more thing for the admin to learn, 
(b) because it's seldom used the admin will be working from 
documentation if it has a problem, and (c) there is no bug-free 
software, therefore the use of LVM on top of RAID will be less reliable 
than a RAID-only solution. I can't quantify that, the net effect may be 
too small to measure. However, the cost and chance of a finger check 
from (a) and (b) are significant.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2006-10-24 23:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 11:25 why partition arrays? Ken Walker
2006-10-19 15:46 ` Doug Ledford
2006-10-21  4:26 ` Bodo Thiesen
2006-10-21 13:39   ` Henrik Holst
2006-10-21 19:25     ` Bodo Thiesen
2006-10-24 23:31     ` Bill Davidsen [this message]
2006-10-25  0:10       ` dean gaudet
2006-10-22 16:02   ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2006-10-18 12:42 martin f krafft
2006-10-18 13:26 ` Doug Ledford
2006-10-18 13:43   ` martin f krafft
2006-10-18 21:42     ` Doug Ledford
2006-10-23 15:59 ` Mario 'BitKoenig' Holbe

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=453EA240.7000407@tmr.com \
    --to=davidsen@tmr.com \
    --cc=bothie@gmx.de \
    --cc=henrik.holst@idgmail.se \
    --cc=ken.walker@manchester.ac.uk \
    --cc=linux-raid@vger.kernel.org \
    /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).