From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Andrew Morton <akpm@osdl.org>,
Tupshin Harper <tupshin@tupshin.com>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: data corruption using raid0+lvm2+jfs with 2.6.0-test3
Date: Fri, 15 Aug 2003 14:27:07 -0700 [thread overview]
Message-ID: <20030815212707.GR1027@matchmail.com> (raw)
In-Reply-To: <16185.29398.80225.875488@gargle.gargle.HOWL>
On Wed, Aug 13, 2003 at 09:05:58AM +1000, Neil Brown wrote:
> On Tuesday August 12, akpm@osdl.org wrote:
> > Tupshin Harper <tupshin@tupshin.com> wrote:
> > >
> > > raid0_make_request bug: can't convert block across chunks or bigger than
> > > 8k 12436792 8
> >
> > There is a fix for this at
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test3/2.6.0-test3-mm1/broken-out/bio-too-big-fix.patch
> >
> > Results of testing are always appreciated...
>
> I don't think this will help. It is a different problem.
>
> As far as I can tell, the problem is that dm doesn't honour the
> merge_bvec_fn of the underlying device (neither does md for that
> matter).
> I think it does honour the max_sectors restriction, so it will only
> allow a request as big as one chunk, but it will allow such a requests
> to span a chunk boundary.
>
> Probably the simplest solution to this is to put in calls to
> bio_split, which will need to be strengthed to handle multi-page bios.
>
> The policy would be:
> "a client of a block device *should* honour the various bio size
> restrictions, and may suffer performance loss if it doesn't;
> a block device driver *must* handle any bio it is passed, and may
> call bio_split to help out".
>
Any progress on this?
next prev parent reply other threads:[~2003-08-15 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 20:45 data corruption using raid0+lvm2+jfs with 2.6.0-test3 Tupshin Harper
2003-08-12 21:08 ` Christophe Saout
2003-08-12 21:10 ` Tupshin Harper
2003-08-12 21:28 ` Andrew Morton
2003-08-12 23:05 ` Neil Brown
2003-08-13 7:25 ` Joe Thornber
2003-08-15 21:27 ` Mike Fedyk [this message]
2003-08-16 8:00 ` Neil Brown
2003-08-16 14:18 ` Lars Marowsky-Bree
2003-08-16 23:52 ` Mike Fedyk
2003-08-17 0:12 ` Neil Brown
2003-08-17 17:50 ` Mike Fedyk
2003-08-17 23:14 ` Neil Brown
2003-08-18 0:28 ` Mike Fedyk
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=20030815212707.GR1027@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=tupshin@tupshin.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