linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Stuart D. Gathman" <stuart@bmsi.com>
To: forums@emat.be,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Flexible storga: LVM setup on top of mdadm sets. Good idea or not?
Date: Sun, 22 Jul 2007 14:57:33 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0707221446080.990-100000@bmsred.bmsi.com> (raw)
In-Reply-To: <46A38AE6.3070805@emat.be>

On Sun, 22 Jul 2007, js wrote:

> I'm looking into making a home brewed nas setup. This is not a 
> production, highly critical environment.
> 
> The result needs to be 1 continuous physical storage space.
> Expandable without reformating, removing data, etc,..
> Acceptable redundancy.
> I don't mind 50% loss of data capacity because of raid 1.  Storage is 
> (relatively) cheap.
> 
> I don't have this material to test.  So it's more like a theoretical setup.
...
> Now my question to you is.  Is this completely bunkers?  Or is it 
> reasonable?

This is how all our systems are setup.  It is the only reasonable way
to do raid1.  Hardware RAID is nasty when you need to add/replace disks
and the new models are bigger.

> Any tips, tricks, advice, comments welcome.

The main drawback to md raid1 is that it always resynchronizes
the *entire* partition when a disk goes offline temporarily.  I also
like to split a drive into several pieces, say split a pair of 240G into two
120G md partitions.  This gives me some flexibility to migrate partitions
between physical drives (for performance tuning, or swapping physical
drives around).  To migrate, set the mirror "faulty" with mdadm,
"hot remove" it, then "hot add" the new partition.  If you don't like
leaving the md drive unmirrored while resyncing to its new location,
reserve 3 physical drives in each md device, but use only 2.  Then
you can a 3rd mirror to migrate, then set faulty and hot remove the
old after the new is finished synchronizing.

Of course, I *hate* having to manually manage the md partitions in Linux.  I
cut my teeth on AIX LVM - which has robust useful raid1 built it.
(The latest experimental LVM mirroring in Linux still doesn't cut it.)
AIX is probably too expensive for home brew, but I understand Open Solaris
has similar features (but haven't had time to try it).

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

  reply	other threads:[~2007-07-22 18:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 16:50 [linux-lvm] Flexible storga: LVM setup on top of mdadm sets. Good idea or not? js
2007-07-22 18:57 ` Stuart D. Gathman [this message]
2007-07-23  7:23   ` Luca Berra
2007-07-23 16:43     ` Stuart D. Gathman
2007-07-24  8:48       ` Luca Berra
2007-07-24  1:44     ` Stuart D. Gathman
2007-07-24  9:13       ` Bryn M. Reeves
2007-08-21  0:33     ` Stuart D. Gathman
2007-08-21  6:52       ` Luca Berra
2007-08-21 14:11         ` Stuart D. Gathman

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=Pine.LNX.4.44.0707221446080.990-100000@bmsred.bmsi.com \
    --to=stuart@bmsi.com \
    --cc=forums@emat.be \
    --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).