All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Reason for md raid 01 blksize limited to 4 KiB?
Date: Wed, 30 May 2012 15:03:16 +0200	[thread overview]
Message-ID: <4FC61A94.3050605@profitbricks.com> (raw)
In-Reply-To: <20120529202559.6aa7fd49@notabene.brown>

On 29/05/12 12:25, NeilBrown wrote:
> On Tue, 29 May 2012 11:30:27 +0200 Sebastian Riemer
> <sebastian.riemer@profitbricks.com> wrote:
>> 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.

Now, I've configured a storage server with real HDDs for testing the
cached IO with kernel 3.4. Here direct IO always doesn't work
(Input/Output error with dd/fio). And cached IO is totally slow. My
RAID0 devices are md100 and md200. The RAID1 on top is the md300.

The md100 is reported as "faulty spare" and this has hit the following a
kernel bug.

This is the debug output:

md/raid0:md100: make_request bug: can't convert block across chunks or
bigger than 512k 541312 320
md/raid0:md200: make_request bug: can't convert block across chunks or
bigger than 512k 541312 320
md/raid1:md300: Disk failure on md100, disabling device.
md/raid1:md300: Operation continuing on 1 devices.
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:1, o:0, dev:md100
disk 1, wo:0, o:1, dev:md200
RAID1 conf printout:
--- wd:1 rd:2
disk 1, wo:0, o:1, dev:md200
md/raid0:md200: make_request bug: can't convert block across chunks or
bigger than 512k 2704000 320

The chunk size of 320 KiB comes from max_sectors_kb of the LSI HW RAID
controller where the drives are passed through as single drive RAID0
logical devices. I guess this is a problem for MD RAID0 underneath the
RAID1, because this doesn't fit as a multiple of the 512 KiB stripe size.

Cheers,
Sebastian

  reply	other threads:[~2012-05-30 13:03 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
2012-05-30 13:03           ` Sebastian Riemer [this message]
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=4FC61A94.3050605@profitbricks.com \
    --to=sebastian.riemer@profitbricks.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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.