linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@keldix.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "Keld Jørn Simonsen" <keld@keldix.com>,
	"Roman Mamedov" <rm@romanrm.ru>,
	"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:40:15 +0200	[thread overview]
Message-ID: <20110506134015.GB22689@www2.open-std.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1105061525520.20305@uplift.swm.pp.se>

On Fri, May 06, 2011 at 03:26:52PM +0200, Mikael Abrahamsson wrote:
> On Fri, 6 May 2011, Keld Jørn Simonsen wrote:
> 
> >I am proposing that we call our raid10 layout types for RAID1 - in 
> >accordance with SNIA standards, and in accordance with the common 
> >understanding as demonstrated by you and others, even here on the 
> >linux-raid kernel mailing list.
> 
> Just so we're clear, if I create a raid1 with 4 drives I want 4 identical 
> copies of the same information, not RAID1+0.
> 
> How should this be handled with your suggestion?

With parameters like the ones that we use today for raid10. Something
like

mdadm --create /dev/md0 --level=1 -n 4 --layout=c4 /dev/sd[abcd]1 

assuming a new layout type "classic" abbreviated as "c". "n4" could also
do for the layout value.

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 13:40 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
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 [this message]
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=20110506134015.GB22689@www2.open-std.org \
    --to=keld@keldix.com \
    --cc=jonnyt@abpni.co.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.ru \
    --cc=swmike@swm.pp.se \
    /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).