All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lord <lord@sgi.com>
To: svetljo <galia@st-peter.stw.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org, linux-xfs@thebarn.com, mkp@mkp.net
Subject: Re: REPOST : linux-2.5.5-xfs-dj1 - 2.5.7-dj2  (raid0_make_request bug)
Date: Fri, 05 Apr 2002 09:20:13 -0600	[thread overview]
Message-ID: <3CADC0AD.4080601@sgi.com> (raw)
In-Reply-To: <3CAD8B9D.8070902@st-peter.stw.uni-erlangen.de>

svetljo wrote:

> Hi
> i'd like to ask you to CC me because i'm not subscribed to the lists
>
> 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
>
> thanks for your help
>
> here is what i found in dmesg
>
>
> XFS mounting filesystem lvm(58,2)
> raid0_make_request bug: can't convert block across chunks or bigger than
> 16k 8323317 64
> raid0_make_request bug: can't convert block across chunks or bigger than
> 16k 8323445 64
> I/O error in filesystem ("lvm(58,2)") meta-data dev 0xc0223a02 block
> 0x601f7d
>         ("xlog_bread") error 5 buf count 131072
> raid0_make_request bug: can't convert block across chunks or bigger than
> 16k 8324829 29
> I/O error in filesystem ("lvm(58,2)") meta-data dev 0xc0223a02 block
> 0x602565
>         ("xlog_bread") error 5 buf count 30208
>

This is your problem, in the 2.5 code base, the bio infrastructure and the
raid code do not work well together. It is being worked on - slowly.

If you want to dumb down xfs to make it function then I suspect you
can do it by editing

    fs/xfs/pagebuf/page_buf.c

looking for the line which uses BIO_MAX_SECTORS and replace

    nr_pages = BIO_MAX_SECTORS >> (PAGE_SHIFT - 9);

with

    nr_pages = 1;

And for extra bonus points, only do it when pb->pb_dev is on the
MD_MAJOR device.

This will make xfs send smaller bio structures down to the block
layer and hopefully avoid the problem.

I have not tested this - don't have any time right now, on a plane
in 6 hours and way too much to do.

Steve



  reply	other threads:[~2002-04-05 15:25 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 [this message]
2002-04-05 16:41 ` Dave Jones
2002-04-05 16:54   ` Stephen Lord
2002-04-05 18:37     ` Andrew Morton
  -- 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=3CADC0AD.4080601@sgi.com \
    --to=lord@sgi.com \
    --cc=galia@st-peter.stw.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@thebarn.com \
    --cc=mkp@mkp.net \
    /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.