From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Jim Lawson <jim+linux-kernel@jimlawson.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.0, SiI3112, md raid1 problem: bio too big device (128 > 15)
Date: Wed, 24 Dec 2003 10:56:06 -0800 [thread overview]
Message-ID: <20031224185606.GZ6438@matchmail.com> (raw)
In-Reply-To: <16361.28564.275984.580859@notabene.cse.unsw.edu.au>
On Wed, Dec 24, 2003 at 09:51:00PM +1100, Neil Brown wrote:
> This is a raid1 bug.
> Some block devices have limits on the sizes of io requests that they
> can handle, and advertise these limits with ->max_sectors and
> ->merge_bvec_fn (and a few others). Any device MUST be able to accept
> a single page IO at any offset.
So, how can I determine the max io request support by my underlying devices
from userspace?
> When raid1 does a 'resync' it does all IO in 64K requests, ignoring
> the restrictions.
> Getting raid1 resync to handle the restrictions is non-trivial (I have
> code, but it is still buggy).
Do you have patches posted anywhere?
> A simple interim fix is to replace
>
> #define RESYNC_BLOCK_SIZE (64*1024)
>
> with
>
> #define RESYNC_BLOCK_SIZE PAGE_SIZE
Then by all means, let's get this into -mm.
Then once the new resync code is ready it can be merged.
next prev parent reply other threads:[~2003-12-24 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 4:37 2.6.0, SiI3112, md raid1 problem: bio too big device (128 > 15) Jim Lawson
2003-12-24 5:06 ` Jeff Garzik
2003-12-24 9:39 ` Andre Hedrick
2003-12-24 10:47 ` Jens Axboe
2003-12-24 10:51 ` Neil Brown
2003-12-24 18:56 ` Mike Fedyk [this message]
2003-12-25 0:27 ` Neil Brown
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=20031224185606.GZ6438@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=jim+linux-kernel@jimlawson.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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