All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@keldix.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: "Keld Jørn Simonsen" <keld@keldix.com>, linux-raid@vger.kernel.org
Subject: Re: wish for Linux MD mirrored raid types
Date: Fri, 6 May 2011 11:03:45 +0200	[thread overview]
Message-ID: <20110506090345.GA22245@www2.open-std.org> (raw)
In-Reply-To: <20110506133159.30c66519@natsu>

On Fri, May 06, 2011 at 01:31:59PM +0600, Roman Mamedov wrote:
> On Fri, 6 May 2011 09:17:52 +0200
> Keld Jørn Simonsen <keld@keldix.com> wrote:
> 
> > I would like linux MD raid10 functionality to be part of the Linux MD
> > RAID1 module, and be called raid1. This is in accordance with the
> > use of the RAID1 term as standadized by SNIA. In fact the RAID10-offset
> > layout is an implementation of a SNIA RAID specification. The RAID10-near
> > layout is an implementation of a simple RAID layout. And the RAID10-far
> > layout is just another layout far a mirrored RAID.  So all these types
> > could just be defined as different RAID1 layouts.
> 
> RAID1 is RAID1, RAID10 is RAID10.
> RAID1 on 4 drives is very different from RAID10 on 4 drives.
> Don't add confusion by trying to rename RAID10 to RAID1.

How are they different?
Say what is the difference between a Linux MD RAID1 with 4 disks, and
the default Linux MD RAID10 with 4 disks? (in the near layout)?

Best regards
keld
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-06  9:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  7:17 wish for Linux MD mirrored raid types Keld Jørn Simonsen
2011-05-06  7:31 ` Roman Mamedov
2011-05-06  9:03   ` Keld Jørn Simonsen [this message]
2011-05-06  9:22     ` Jonathan Tripathy
2011-05-06  9:41       ` Keld Jørn Simonsen
2011-05-06  9:50         ` Roman Mamedov
2011-05-06 10:05           ` Jonathan Tripathy
2011-05-06 10:54             ` David Brown
2011-05-06 13:27               ` Keld Jørn Simonsen
2011-05-06 14:01                 ` Miles Fidelman
2011-05-06 15:24                   ` Keld Jørn Simonsen
2011-05-06 15:34                     ` Roberto Spadim
2011-05-06 16:23                       ` Miles Fidelman
2011-05-06 18:29                       ` Keld Jørn Simonsen
2011-05-06 20:30                 ` Leslie Rhorer
2011-05-06 20:43                   ` Miles Fidelman
2011-05-06 12:33           ` Keld Jørn Simonsen
2011-05-06 13:26             ` Mikael Abrahamsson
2011-05-06 13:40               ` Keld Jørn Simonsen
2011-05-06  7:51 ` David Brown
2011-05-06  9:27   ` Keld Jørn Simonsen
2011-05-08 18:14 ` Luca Berra
2011-05-08 21:25   ` Miles Fidelman
2011-05-09  3:40     ` Keld Jørn Simonsen
2011-05-09  4:24       ` NeilBrown
2011-05-09 19:57         ` Keld Jørn Simonsen
2011-05-09  5:22 ` Emmanuel Noobadmin
2011-05-09 14:48   ` Roberto Spadim
2011-05-09 19:59   ` Keld Jørn Simonsen
2011-05-09 20:12     ` Roberto Spadim

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=20110506090345.GA22245@www2.open-std.org \
    --to=keld@keldix.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.ru \
    /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.