From: NeilBrown <neilb@suse.de>
To: Sebastian Riemer <sebastian.riemer@profitbricks.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Reason for md raid 01 blksize limited to 4 KiB?
Date: Tue, 29 May 2012 20:25:59 +1000 [thread overview]
Message-ID: <20120529202559.6aa7fd49@notabene.brown> (raw)
In-Reply-To: <4FC49733.9050905@profitbricks.com>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
On Tue, 29 May 2012 11:30:27 +0200 Sebastian Riemer
<sebastian.riemer@profitbricks.com> wrote:
> On 28/05/12 06:05, NeilBrown wrote:
> > What do you mean by "doesn't work"? Returns errors? crashes? hangs? kills
> > you cat?
> >
>
> dd with oflag=direct returned an IO error.
Odd. Updating mdadm shouldn't affect that.
>
> > It works for me.
> >
> > When I use 32K direct writes to a RAID1, both underlying RAID0 arrays see
> > 64-sector writes.
> >
> > (when I do normal buffered writes I see 8-sector writes which seems odd,
> > but clearly md/RAID1 is allowing large writes through)
> >
>
> Now, I've updated mdadm to version 3.2.5 and it works like you've
> described it. Thanks for your help! But the buffered IO is what matters.
> 4k isn't enough there. Please inform me about changes which increase the
> size in buffered IO. I'll have a look at this, too.
I don't know. I'd have to dive into the code and look around and put a few
printks in to see what is happening.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-29 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 8:43 Reason for md raid 01 blksize limited to 4 KiB? Sebastian Riemer
2012-05-21 23:14 ` Stan Hoeppner
2012-05-21 23:28 ` NeilBrown
2012-05-25 12:35 ` Sebastian Riemer
2012-05-28 4:05 ` NeilBrown
2012-05-29 9:30 ` Sebastian Riemer
2012-05-29 10:25 ` NeilBrown [this message]
2012-05-30 13:03 ` Sebastian Riemer
2012-05-31 5:42 ` NeilBrown
2012-05-31 6:18 ` Yuanhan Liu
2012-05-31 10:26 ` Sebastian Riemer
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=20120529202559.6aa7fd49@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=sebastian.riemer@profitbricks.com \
/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).