From: "D.S. Ljungmark" <spider@skuggor.se>
To: linux-raid@vger.kernel.org
Cc: Spider <spider@skuggor.se>
Subject: md-raid and block sizes
Date: Mon, 27 Dec 2010 13:00:28 +0100 [thread overview]
Message-ID: <1293451228.3266.9.camel@Waves.darkmere> (raw)
Hello,
With the advent of the WD*EARS drives and the "advanced partitioning"
system that requires 4k blocks, I wanted to pop a quick question to see
how the md metadata is aligned and how it should be aligned to get
proper performance out of the devices.
So, For raid1, I'll assume there is some metadata-overhead on the
drives, how large is this block? Will there be need to make a partition
on the md-device in order to get proper alignment of filesystem =>
platters?
for both raid1 and 5/6 levels, what are the appropiate stride-sizes for
ext3/4?
For more advanced raid configurations (5-6), how should the ext3/4
stripe size be configured?
Yes, a lot of similarly naive questions, however, I'm asking mostly
because of how devices are changing from 512 to 4k sized blocks, with
quite interesting changes in performance, and I wanted to figure out
what is the current state of software raid. At which "level" of the
stack: (partition) raid (partition) filesystem , do you have to account
for the block sizes in order to not degrade performance of the devices.
( In a perfect world I'd be able to purchase a stack of the devices and
test for myself and come back with a report. However, money and hardware
is a scarce resource ;)
ps. please keep me CC'd as I'm not subscribed to the list.
// Spider
next reply other threads:[~2010-12-27 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 12:00 D.S. Ljungmark [this message]
2010-12-27 19:02 ` md-raid and block sizes Doug Dumitru
2010-12-28 11:45 ` John Robinson
[not found] ` <AANLkTikWxCxVUO+O8MXRXRR7Y8R5xGC1Catv-EiNGcDj@mail.gmail.com>
2010-12-28 8:46 ` D.S. Ljungmark
2010-12-28 11:29 ` hansbkk
2010-12-28 11:45 ` Neil Brown
2010-12-28 11:50 ` Mikael Abrahamsson
2010-12-28 11:51 ` Roman Mamedov
2010-12-28 11:45 ` Roman Mamedov
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=1293451228.3266.9.camel@Waves.darkmere \
--to=spider@skuggor.se \
--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 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).