linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: keld@keldix.com
To: Gionatan Danti <g.danti@assyoma.it>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 10 far and offset on-disk layouts
Date: Fri, 27 Dec 2013 16:19:27 +0100	[thread overview]
Message-ID: <20131227151927.GA4003@www5.open-std.org> (raw)
In-Reply-To: <52BD8EDD.10809@assyoma.it>

On Fri, Dec 27, 2013 at 03:29:49PM +0100, Gionatan Danti wrote:
> Hi all,
> I (think of) quite well understand how far and offset work, but I can 
> not find any data on the precise on-disk layout.
> 
> FAR LAYOUT
> md(4) states:
> "The first copy of all data blocks will be striped across the early part 
> of all drives in RAID0 fashion, and then the next copy of all blocks 
> will be striped across a later section of all drives, always ensuring 
> that all copies of any given block are on different drives"
> 
> The "on different drives" part let me wonder _how_ are chunks 
> distributed. On a 4-disk array, I can imagine some different schemas:
> 
> 1)	A1 A2 A3 A4
> 	.. .. .. ..
> 	A4 A1 A2 A3
> 
> 2)	A1 A2 A3 A4
> 	.. .. .. ..
> 	A2 A1 A4 A3
> 
> The first schema is the one depicted by SuSe documentation [1], while 
> the second is the one described by Wikipedia [2].
> 
> Question 1: as the two schema have different reliability 
> characteristics, which is really used?

The wikipedia description is what you get for new arrays with newer
kernels, while the suse documentation is what you will get with older kernels.
The wikipedia layout was made because there are better chances of recovery,
Chances went from 1/3 to 2/3 with eg 4 drives, when 2 drives were failing.

I would say that the Suse description is just not updated.

Best regards
Keld

  parent reply	other threads:[~2013-12-27 15:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 14:29 RAID 10 far and offset on-disk layouts Gionatan Danti
2013-12-27 14:46 ` Peter Grandi
2013-12-27 15:16 ` Gionatan Danti
2013-12-27 17:16   ` Peter Grandi
2013-12-27 17:32     ` Gionatan Danti
2013-12-27 18:26       ` keld
2013-12-27 15:19 ` keld [this message]
2013-12-27 15:22   ` Gionatan Danti
2013-12-27 15:49     ` keld
2014-01-09  8:03       ` Gionatan Danti
2014-01-12 23:20         ` NeilBrown
2014-01-13  8:52           ` Gionatan Danti
2014-01-13  9:45             ` NeilBrown
2014-01-13 10:15               ` Gionatan Danti
2014-01-13 22:27                 ` NeilBrown
2014-01-13 23:38                   ` keld
2014-01-14  0:46                     ` Stan Hoeppner
2014-01-14  9:38                       ` keld
2014-01-14  9:06                   ` Gionatan Danti
2014-01-14  9:16                     ` NeilBrown
2014-01-14  9:27                       ` Gionatan Danti
2014-01-14 10:06               ` keld

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=20131227151927.GA4003@www5.open-std.org \
    --to=keld@keldix.com \
    --cc=g.danti@assyoma.it \
    --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).