From: James Braid <jamesb@loreland.org>
To: linux-raid@vger.kernel.org
Subject: chunk size must be power of two?
Date: Wed, 06 Dec 2006 21:29:06 +0000 [thread overview]
Message-ID: <45773622.8020704@loreland.org> (raw)
Is there any reason the chunk size has to be a power of two?
We're trying to use md devices to stripe over hardware RAID5 arrays, so
to align the I/O correctly, I want to set the chunk size to (n - 1) *
stripe_size for the underlying array. Which is impossible to do because
mdadm (and the kernel) insist on the chunk size being a power of two.
I haven't tried just removing the kernel checks yet ... is there a
reason why md is limited to power of two chunk sizes?
Failing that, does anyone know of anything else I can use to stripe
block devices together which doesn't have the power of two limitation?
device-mapper/LVM seems to have the same problem...
next reply other threads:[~2006-12-06 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 21:29 James Braid [this message]
2006-12-06 21:54 ` chunk size must be power of two? Neil Brown
2006-12-07 0:16 ` James Braid
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=45773622.8020704@loreland.org \
--to=jamesb@loreland.org \
--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).