public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.7 thoughts
Date: Fri, 10 Oct 2003 20:49:51 -0700	[thread overview]
Message-ID: <20031011034951.GE4716@pegasys.ws> (raw)
In-Reply-To: <20031010182918.GF1084@marowsky-bree.de>

On Fri, Oct 10, 2003 at 08:29:18PM +0200, Lars Marowsky-Bree wrote:
> On 2003-10-10T08:30:03,
>    Kevin Corry <kevcorry@us.ibm.com> said:
> 
> > On Friday 10 October 2003 01:19, Stuart Longland wrote:
> > > 	- Software RAID 0+1 perhaps?
> 
> Because RAID 0+1 is a rather bad idea. You want RAID 1+0. Make up the
> fault matrix and simulate what happens if drives fail.
> 
> We can do both though, as Kevin pointed out. So if you want to shot
> yourself in the foot, in the best Unix tradition, we allow you to ;)

I concur with one caviat.  0+1 has the advantage of
extendability that doesn't exist with 1+0.

	1. break mirror downing side A
	2. break stripe A
	3. build new stripe A with added disk(s)
	4. copying stripe B to stripe A
	5. break stripe B
	6. build new stripe B with added disk(s)
	7. build mirror (A->B)

It may even be possible to do this live.  So if gradual
extendability is more important than surviving multiple
failures 0+1 has the advantage.  Normally i prefer the
reliability or to do striping at the logical volume level.


	
	


-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  reply	other threads:[~2003-10-11  3:49 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09  8:08 2.7 thoughts Frederick, Fabian
2003-10-09  8:55 ` John Bradford
2003-10-09  9:45   ` mario noioso
2003-10-09 11:58 ` Gábor Lénárt
2003-10-09 14:57   ` Stephan von Krawczynski
2003-10-10  6:19     ` Stuart Longland
2003-10-10  6:30       ` William Lee Irwin III
2003-10-10  7:30         ` YoshiyaETO
2003-10-10  7:40           ` William Lee Irwin III
2003-10-10  8:47             ` YoshiyaETO
2003-10-10  9:09               ` William Lee Irwin III
2003-10-10 10:26                 ` YoshiyaETO
2003-10-10 10:50                   ` William Lee Irwin III
2003-10-10 10:55                     ` William Lee Irwin III
2003-10-10 10:51       ` Stephan von Krawczynski
2003-10-10 14:07         ` Stuart Longland
2003-10-10 14:27           ` Stephan von Krawczynski
2003-10-10 14:35           ` Gábor Lénárt
2003-10-10 14:47             ` William Lee Irwin III
2003-10-10 14:48               ` Mark Mielke
2003-10-10 15:01                 ` William Lee Irwin III
2003-10-10 15:50                   ` Mark Mielke
2003-10-10 16:35                     ` Chris Friesen
2003-10-10 16:44                       ` William Lee Irwin III
2003-10-12 20:14                   ` Pavel Machek
2003-10-10 15:12               ` Jamie Lokier
2003-10-10 15:21                 ` William Lee Irwin III
2003-10-10 18:03               ` Tim Hockin
2003-10-10 18:29                 ` William Lee Irwin III
2003-10-10 18:56                   ` Tim Hockin
2003-10-10 23:40                     ` Rusty Russell
2003-10-15 19:15           ` Anton Blanchard
2003-10-10 13:30       ` Kevin Corry
2003-10-10 18:29         ` Lars Marowsky-Bree
2003-10-11  3:49           ` jw schultz [this message]
2003-10-11 13:24             ` Lars Marowsky-Bree
2003-10-11 19:50               ` jw schultz
2003-10-10 17:12       ` Matt Simonsen
2003-10-10 20:59   ` Pedro Larroy
2003-10-09 18:17 ` Greg KH
2003-10-09 19:07 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-10-09 11:56 Svetoslav Slavtchev
2003-10-09 12:44 Xose Vazquez Perez
2003-10-09 13:17 Frederick, Fabian
2003-10-09 13:19 ` Jens Axboe
2003-10-09 13:50 ` Gábor Lénárt
2003-10-09 13:52 ` Bartlomiej Zolnierkiewicz
2003-10-10 19:01 Zwane Mwaikambo

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=20031011034951.GE4716@pegasys.ws \
    --to=jw@pegasys.ws \
    --cc=linux-kernel@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