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: Sat, 16 Aug 2003 16:52:45 -0700 [thread overview]
Message-ID: <20030816235245.GU1027@matchmail.com> (raw)
In-Reply-To: <16189.58517.211393.526998@gargle.gargle.HOWL>
On Sat, Aug 16, 2003 at 06:00:21PM +1000, Neil Brown wrote:
> On Friday August 15, mfedyk@matchmail.com wrote:
> > 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
>
> > >
> > > 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?
>
> No, and I doubt there will be in a big hurry, unless I come up with an
> easy way to make lvm-over-raid0 break instantly instead of eventually.
>
> I think that for now you should assume tat lvm over raid0 (or raid0
> over lvm) simply isn't supported. As lvm (aka dm) supports striping,
> it shouldn't be needed.
I have a raid5 with "4" 18gb drives, and one of the "drives" is two 9gb
drives in a linear md "array".
I'm guessing this will hit this bug too?
I have a couple systems that use software raid5 that I'll avoid putting
2.6-test on until I know the raid is more reliable (or is this only with
md+lvm?)
next prev parent reply other threads:[~2003-08-16 23:52 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
2003-08-16 8:00 ` Neil Brown
2003-08-16 14:18 ` Lars Marowsky-Bree
2003-08-16 23:52 ` Mike Fedyk [this message]
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=20030816235245.GU1027@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;
as well as URLs for NNTP newsgroup(s).