linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan /*St0fF*/ Hübner" <st0ff.npl@googlemail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: MD RAID Bug 7/15/12
Date: Tue, 02 Oct 2012 00:27:56 +0200	[thread overview]
Message-ID: <506A18EC.1040602@gmail.com> (raw)
In-Reply-To: <B09EC2F5-55B5-48A8-B427-81277CF3D136@colorremedies.com>

Am 01.10.2012 00:16, schrieb Chris Murphy:
> 
> On Sep 30, 2012, at 3:08 PM, Stefan /*St0fF*/ Hübner wrote:
> 
> 
>> Also off topic: 12 drives would be as "nearly unalignable" as 19 are.
> 
> I'm not sure what you mean by unalignable. A separate question is if a 4K chunks size is a good idea, even with 24 disks, but I'm unsure of the usage and workload.
> 
> 
[...]
By that I mean that optimal alignment has to do with a reasonable chunk
size and an amount of data disks that is/should be a power of two.  If
you made a databases commit chunk size 64k, you'd create maybe a raid6
of 6 drives with a 16k chunk size.  That way you'd spare many many
read-modify-write operations, as on every commit it'd write all 6 disks
once and no rmw would happen.  You'd also have to take care of proper
partition placement.

That probably is what you know as alignment.  I just want to make it
more concious that not only the placement of a data partition goes into
alignment, also the size of a "normal" data packet relative to chunk
size and amount of disks used.

cheers,
stefan

--
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:[~2012-10-01 22:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-30  0:12 MD RAID Bug 7/15/12 Mark Munoz
2012-09-30  2:47 ` Chris Murphy
2012-09-30 21:08   ` Stefan /*St0fF*/ Hübner
2012-09-30 22:16     ` Chris Murphy
2012-10-01 22:27       ` Stefan /*St0fF*/ Hübner [this message]
2012-10-01  3:02 ` NeilBrown
     [not found]   ` <42BA87F6-C5A3-4321-A4C7-0DCF0A9DF79D@rightthisminute.com>
2012-10-02  1:51     ` Mark Munoz
2012-10-02  2:25       ` NeilBrown
     [not found]     ` <20121002114920.1029bed7@notabene.brown>
2012-10-02  2:33       ` Mark Munoz
2012-10-02  5:07         ` NeilBrown
2012-10-02 22:53           ` Mark Munoz
2012-10-03  1:54             ` NeilBrown

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=506A18EC.1040602@gmail.com \
    --to=st0ff.npl@googlemail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=st0ff@npl.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).