From: keld@keldix.com
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: NeilBrown <neilb@suse.de>, Gionatan Danti <g.danti@assyoma.it>,
linux-raid@vger.kernel.org
Subject: Re: RAID 10 far and offset on-disk layouts
Date: Tue, 14 Jan 2014 10:38:34 +0100 [thread overview]
Message-ID: <20140114093834.GB4077@www5.open-std.org> (raw)
In-Reply-To: <52D488D7.4080604@hardwarefreak.com>
On Mon, Jan 13, 2014 at 06:46:15PM -0600, Stan Hoeppner wrote:
> On 1/13/2014 5:38 PM, keld@keldix.com wrote:
> > On Tue, Jan 14, 2014 at 09:27:51AM +1100, NeilBrown wrote:
> ...
> >> So this change:
> >>
> >> http://en.wikipedia.org/w/index.php?title=Non-standard_RAID_levels&diff=501908270&oldid=501604733
> >>
> >> was wrong.
> >
> > Well, it was me doing the wikipedia edit. The edit was done based on information from Neil that this was actually
> > the layout. Then later we found out that it really was not, but it should be; and then Neil implemented
> > the better layout. Maybe it is not called "f2", I look forward to be informed what the actual name
> > will be.
> >
> > I think the name should be "f2" as it is a "far" layout, with 2 copies, and it really should be
> > the default for "far" with 2 copies, as the redundancy is much better than the old layout.
> > Keeping the name would mean that we would not need to make and spread documentation on this,
> > so that people following existing documentation would automatically get the better implementation.
> > There is no need that new raid instances of "far" should get the old layout, except for
> > backwards compatibility.
>
> The problem here is that you're creating the Wikipedia page as if it
> *is* source reference material. I.e. you're including "original work,
> your original work. This is a violation of the Wikipedia rules of
> editing. And this kind of situation is exactly why those rules exist.
I am only referencing material available other places.
> The layout tables you are including need to exist in a free to duplicate
> reference document, and should be copied verbatim from said document.
> They should not be created from scratch simply based on information in
> an email exchange on a mailing list, just as web forums are not
> considered a valid reference source.
I only described things that was already described.
best regards
keld
next prev parent reply other threads:[~2014-01-14 9:38 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 [this message]
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=20140114093834.GB4077@www5.open-std.org \
--to=keld@keldix.com \
--cc=g.danti@assyoma.it \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stan@hardwarefreak.com \
/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).