All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: keld@keldix.com, CoolCold <coolthecold@gmail.com>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: XFS on top RAID10 with odd drives count and 2 near copies
Date: Wed, 15 Feb 2012 07:30:45 -0600	[thread overview]
Message-ID: <4F3BB385.4000608@hardwarefreak.com> (raw)
In-Reply-To: <20120215083058.GA8821@cthulhu.home.robinhill.me.uk>

On 2/15/2012 2:30 AM, Robin Hill wrote:
> On Tue Feb 14, 2012 at 05:27:43PM -0600, Stan Hoeppner wrote:
> 
>> Maybe I simply don't understand this 'magic' of the f2 and far layouts.
>>  If you only read the "faster half" of a spindle, does this mean writes
>> go to the slower half?  If that's the case, how can you read data that's
>> never been written?
>>
> Writes go to both halves, as normal for a mirrored setup, which is why

Huh?  A 'normal' RAID setup mirrors one disk to another.  You're
describing data being mirrored from the outer half of a single disk to
the inner half.  Where's the Redundancy in this?  This doesn't make sense.

> its write performance is lower than that of a near layout array (more
> head movement required). Reads will (normally) come from the faster
> (outer) half of the disk though, so read performance is better. In most
> cases workloads are read-heavy, so this comes out as a significant gain.

Again, this makes no sense.  You're simply repeating what David said.
Neither of you seem to really understand this, or are simply unable to
explain it correctly, technically.

Maybe Neil will jump into the fray and answer my original question.

-- 
Stan

  reply	other threads:[~2012-02-15 13:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 15:17 XFS on top RAID10 with odd drives count and 2 near copies CoolCold
2012-02-11  4:05 ` Stan Hoeppner
2012-02-11 14:32   ` David Brown
2012-02-12 20:16   ` CoolCold
2012-02-13  8:50     ` David Brown
2012-02-13  9:46       ` CoolCold
2012-02-13 11:19         ` David Brown
2012-02-13 13:46       ` Stan Hoeppner
2012-02-13  8:54     ` David Brown
2012-02-13  9:49       ` CoolCold
2012-02-13 12:09     ` Stan Hoeppner
2012-02-13 12:42       ` David Brown
2012-02-13 14:46         ` Stan Hoeppner
2012-02-13 21:40       ` CoolCold
2012-02-13 23:02         ` keld
2012-02-14  3:49           ` Stan Hoeppner
2012-02-14  8:58             ` David Brown
2012-02-14 11:38             ` keld
2012-02-14 23:27               ` Stan Hoeppner
2012-02-15  8:30                 ` Robin Hill
2012-02-15 13:30                   ` Stan Hoeppner [this message]
2012-02-15 14:03                     ` Robin Hill
2012-02-15 15:40                     ` David Brown
2012-02-17 13:16                       ` Stan Hoeppner
2012-02-17 14:57                         ` David Brown
2012-02-17 19:30                           ` Peter Grandi
2012-02-18 13:59                             ` David Brown
2012-02-19 14:46                           ` Peter Grandi
2012-02-17 19:03                         ` Peter Grandi
2012-02-17 22:12                           ` Stan Hoeppner
2012-02-18 17:09                           ` Peter Grandi
2012-02-15  9:24                 ` keld
2012-02-15 12:10                 ` David Brown
2012-02-15 13:08                   ` keld
2012-02-17 18:44                 ` Peter Grandi
2012-02-18 17:39                   ` Peter Grandi
2012-02-14  7:31           ` CoolCold
2012-02-14  9:05             ` David Brown
2012-02-14 11:10               ` Stan Hoeppner
2012-02-14  2:49         ` Stan Hoeppner

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=4F3BB385.4000608@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=coolthecold@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.