From: Gionatan Danti <g.danti@assyoma.it>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, keld@keldix.com,
Gionatan Danti <g.danti@assyoma.it>
Subject: Re: RAID 10 far and offset on-disk layouts
Date: Tue, 14 Jan 2014 10:27:12 +0100 [thread overview]
Message-ID: <52D502F0.2090703@assyoma.it> (raw)
In-Reply-To: <20140114201655.61f4e10b@notabene.brown>
>> Ok, so let recap:
>>
>> 1) FAR layout is the one depicted by SuSe documentation, while the
>> Wikipedia entry is wrong
>
> Yes.
>
>>
>> 2) MD _can_ produce a FAR layout as depicted by Wikipedia, but we don't
>> know how the user-space mdadm tool call it (maybe it is not implemented
>> yet?)
>
> Yes. Not implemented yet.
>
>>
>> 3) There are any reasons why FAR and OFFSET layout scramble data in this
>> manner, coupling any disk with two more disks? It was done for
>> simplicity, or I am missing something?
>
> It just seemed the easiest thing to do at the time.
>
>>
>> 4) you confirm that currently we can _not_ create a FAR layout as the
>> one depicted by wikipedia by no means? What about OFFSET layout?
>
> You certainly can created the FAR layout depicted on wikipedia, e.g. by
> binary-editing the metadata on some devices, or writing some code which does
> that for you. It requires flipping one bit in the metadata and updating the
> checksum. You can probably even to it by writing something appropriate into
> some sysfs files.
> But mdadm cannot do it yet.
> Ditto for the new OFFSET layout.
> (The old offset layout can be created with "--layout=o2").
>
> NeilBrown
>
All clear now :)
Thank you very much Neil.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2014-01-14 9:27 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
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 [this message]
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=52D502F0.2090703@assyoma.it \
--to=g.danti@assyoma.it \
--cc=keld@keldix.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).