From: Roman Mamedov <rm@romanrm.ru>
To: "Keld Jørn Simonsen" <keld@keldix.com>
Cc: Jonathan Tripathy <jonnyt@abpni.co.uk>, linux-raid@vger.kernel.org
Subject: Re: wish for Linux MD mirrored raid types
Date: Fri, 6 May 2011 15:50:59 +0600 [thread overview]
Message-ID: <20110506155059.6f82cbeb@natsu> (raw)
In-Reply-To: <20110506094102.GC22245@www2.open-std.org>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
On Fri, 6 May 2011 11:41:02 +0200
Keld Jørn Simonsen <keld@keldix.com> wrote:
> > RAID1 is traditionally a mirror only setup (ok, some RAID
> > implementations may do some load-balancing of some sort). So a RAID1
> > with 4 disks is one data set copied onto 4 disks. Bandwidth is roughly
> > the same as a single disk (ignoring any load balancing).
> > RAID10 is mirror and stripe. A RAID10 with 4 disks is similar to a 2
> > disk RAID0 (double bandwidth with data split in half across both disks),
> > but with each disk having a mirror (which brings the total up to 4 drives).
> >
> > Additionally, a RAID1 disk (at least using MD) can be accessed just like
> > a normal disk (good for recovery etc.) however a single disk out of a
> > RAID10 array is next to useless.
>
> I think you are demonstrating some of my points about general knowledge
> quite nicely. Don't worry, you are not alone.
So what is your proposal: people do not know they can do X, but commonly do Y,
so let's rename X to Y so that both things are called Y and they 'know how to
do it'?
RAID10 is an established term and means "stripe of mirrors", period.
RAID1 means just a mirror. All the rest is just implementation details.
Trying to redefine 2x2 to be 5 as some 'educational project' is definitely
misguided.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-06 9:50 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
2011-05-06 9:22 ` Jonathan Tripathy
2011-05-06 9:41 ` Keld Jørn Simonsen
2011-05-06 9:50 ` Roman Mamedov [this message]
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=20110506155059.6f82cbeb@natsu \
--to=rm@romanrm.ru \
--cc=jonnyt@abpni.co.uk \
--cc=keld@keldix.com \
--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).