From: Andrew Morton <akpm@zip.com.au>
To: Stephen Lord <lord@sgi.com>
Cc: Dave Jones <davej@suse.de>,
svetljo <galia@st-peter.stw.uni-erlangen.de>,
linux-kernel@vger.kernel.org, linux-xfs@thebarn.com
Subject: Re: REPOST : linux-2.5.5-xfs-dj1 - 2.5.7-dj2 (raid0_make_request bug)
Date: Fri, 05 Apr 2002 10:37:41 -0800 [thread overview]
Message-ID: <3CADEEF5.1A73C602@zip.com.au> (raw)
In-Reply-To: <3CAD8B9D.8070902@st-peter.stw.uni-erlangen.de> <20020405184103.F14828@suse.de> <3CADD6CA.8010600@sgi.com>
Stephen Lord wrote:
>
> Dave Jones wrote:
>
> >On Fri, Apr 05, 2002 at 01:33:49PM +0200, svetljo wrote:
> > > i'm having some interesting troubles
> > > i have lvm over soft RAID-0 with LV's formated with XFS and JFS
> > > i can work with the JFS LV's,
> > > but i can not with the XFS one's, i can not mount them ( no troubles
> > > with XFS normal partitions)
> > > so i'd like to ask is this problem with XFS or with raid or lvm
> > > and is there a way to fix it
> >
> >IIRC, this was reported a while ago, and it was something to do with
> >XFS creating too large requests that upset the raid code.
> >
> Or the raid code not handling the bio layer too well, depends on your point
> of view ;-)
>
Stephen's point of view is correct. RAID0 fails
in the same manner with the large pagecache BIOs
which I'm feeding it. It fails in the same manner
with O_DIRECT on ext2.
Neil knows about it, and will get to it. mkp has
a 2.4 request splitter which he will turn into a
2.5 BIO splitter.
As you said - it's being worked on.
-
next prev parent reply other threads:[~2002-04-05 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 11:33 REPOST : linux-2.5.5-xfs-dj1 - 2.5.7-dj2 (raid0_make_request bug) svetljo
2002-04-05 15:20 ` Stephen Lord
2002-04-05 16:41 ` Dave Jones
2002-04-05 16:54 ` Stephen Lord
2002-04-05 18:37 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 8:14 svetljo
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=3CADEEF5.1A73C602@zip.com.au \
--to=akpm@zip.com.au \
--cc=davej@suse.de \
--cc=galia@st-peter.stw.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@thebarn.com \
--cc=lord@sgi.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 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.