All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>
To: Graham Mitchell <gmitch@woodlea.com>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: device and partition alignment
Date: Sat, 05 Jun 2010 23:51:32 +0200	[thread overview]
Message-ID: <4C0AC6E4.4080408@stud.tu-ilmenau.de> (raw)
In-Reply-To: <000b01cb04f0$dbcf7720$936e6560$@woodlea.com>

Hi Graham,

I guess you couldn't find much about this as it has more to do with
common sense than magic formulae.  If you have 4k-sector drives, align
everything at multiples of 4k, use filesystem-units of multiples of 4k.
 As I read and it also seems very logical from the ATA / SCSI point of
view, a stripe size of 256k seems most straight forward.  This is the
largest amount of data (a.t.m.) that can be read or written with a
single command to a disk.

What should I say more?  Well, block 63 is too oldschool, coming from
the CHS-alignment of old disks.  It doesn't make any sense nowadays.

My suggestion:
- use GPT partitioning (for safeness into the future)
- align the first partition at block 64
- use a filesystem chunk size of at least 4k (depending on the data you
want to store you might use even larger chunks)

Hope it helps,
Stefan

Am 05.06.2010 22:51, schrieb Graham Mitchell:
> I've spent the last couple of days doing some googling, and my goodle-fu
> seems to have deserted me at the moment.
> 
> I'm looking for some guides and/or words of wisdom on how to partition disks
> with optimal alignment for RAID devices, and also the same for laying file
> systems on those devices. I've just (re)created a 15 drive RAID 6 array, and
> I've partitioned the disk, and I'm building the array on partition 1, which
> I see starts at block 63 - I am guessing that this is non-optimal? Is there
> a magic formula that can be used to work out what the optimal starting block
> on the disk should be, so that we can avoid (or at least reduce) the
> read/modify/write penalty on the physical drives?
> 
> Is there also a magic formula for doing the same for file systems laid down
> on a RAID device? I guess that this would depend on the type of superblock
> used, since there seems to be different locations (start, end, start +4k)
> for it. 
> 
> I've read thru the manual pages (shocking I know), and I can't see anything
> mentioned in there, and there's certainly no --optimal-alignment option
> there (any chance for next version - lol).
> 
> Can someone point me in the direction of some reading about this please?
> 
> Thanks.
> 
> 
> Graham
> 
> --
> 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:[~2010-06-05 21:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 20:51 device and partition alignment Graham Mitchell
2010-06-05 21:51 ` Stefan /*St0fF*/ Hübner [this message]
2010-06-05 22:11   ` Wolfgang Denk
2010-06-05 23:14     ` Graham Mitchell
2010-06-06  0:05       ` Leslie Rhorer
2010-06-06  0:19         ` Graham Mitchell
2010-06-06 10:56       ` Stefan /*St0fF*/ Hübner

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=4C0AC6E4.4080408@stud.tu-ilmenau.de \
    --to=stefan.huebner@stud.tu-ilmenau.de \
    --cc=gmitch@woodlea.com \
    --cc=linux-raid@vger.kernel.org \
    --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 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.