public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Tapani Tarvainen <raid@tapanitarvainen.fi>
Cc: linux-raid@vger.kernel.org
Subject: Re: Draft Mirrored Linux Mini How-to
Date: Sat, 08 Aug 2009 03:11:59 +0200	[thread overview]
Message-ID: <87vdkzp0rk.fsf@frosties.localdomain> (raw)
In-Reply-To: <20090807035303.GA31754@musti.tarvainen.info> (Tapani Tarvainen's message of "Fri, 7 Aug 2009 06:53:03 +0300")

Tapani Tarvainen <raid@tapanitarvainen.fi> writes:

> On Thu, Aug 06, 2009 at 08:08:47PM -0400, Harold Pritchett (harold@uga.edu) wrote:
>
>> Mirrored Linux Mini How-to
>
> A few quick observations:
>
>> Install linux on two identical disk drives in such a way that the failure
>> of either of the drives will allow the system to be recovered without any
>> loss of data
>>
>> Both of the drives are partitioned exactly the same:
>>      1.  3 primary partitions
>>      2.  Partition 1 - size - 1GB format as Linux Raid (fd)
>>      3.  Partition 2 - size = real memory size, format as linux swap (82)
>>      4.  Partition 3 = size = remainder of disk, format as linux raid (fd)
>
> If I read correctly, you are not only leaving swap out of lvm,
> you are not mirroring it at all - which would make the system
> crash if the swap disk breaks.
> Putting swap on lvm would also allow growing it easily as needed.

On the other hand don't forget that raid1 is buggy with swap and the
page contents might change between writes to the first and second
disk. Or has that been fixed?

> Another point is that sometimes it is useful to have multiple
> partitions separately mirrored and then combined with lvm:
> it allows things like changing the raid configuration from
> two-disk raid1 to three-disk raid5 without moving data
> via backup and yet avoiding windows of vulnerability
> to single-disk failure during the transition.
> (Perhaps not common enough to be worth mentioning here,
> but I've found it useful.)

You can transform raid1 to raid5 without loss of redundncy so I don't
quite see what you mean here.

MfG
        Goswin

  reply	other threads:[~2009-08-08  1:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A78292A.5000607@in.ibm.com>
     [not found] ` <1249421223.18245.36.camel@pasglop>
2009-08-05  9:17   ` 2.6.31-rc5-git2 crash on a idle system Sachin Sant
2009-08-05  9:52     ` Benjamin Herrenschmidt
2009-08-06 13:33       ` Sachin Sant
2009-08-06 13:40         ` Michael Ellerman
2009-08-06 21:51         ` Benjamin Herrenschmidt
2009-08-07  0:08           ` Draft Mirrored Linux Mini How-to Harold Pritchett
2009-08-07  2:09             ` Goswin von Brederlow
2009-08-07  3:53             ` Tapani Tarvainen
2009-08-08  1:11               ` Goswin von Brederlow [this message]
2009-08-08  1:41                 ` NeilBrown
2009-08-08  7:59                   ` Goswin von Brederlow
2009-08-08 15:24                     ` John Robinson
2009-08-08 14:09                   ` Bill Davidsen
2009-08-07  8:10             ` Fredrik Pettersson
2009-08-07  9:51             ` Keld Jørn Simonsen
     [not found]               ` <4A7C5BD2.80508@uga.edu>
     [not found]                 ` <20090807173423.GA32127@rap.rap.dk>
2009-08-08 11:36                   ` Keld Jørn Simonsen
2009-08-07 15:27             ` Draft Mirrored Linux Mini How-to - sfdisk suggestion Maurice Hilarius
2009-08-08  1:13               ` Goswin von Brederlow
2009-08-09 18:55     ` 2.6.31-rc5-git2 crash on a idle system Louwrentius

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=87vdkzp0rk.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=raid@tapanitarvainen.fi \
    /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