From: svetljo <galia@st-peter.stw.uni-erlangen.de>
To: lord@sgi.com
Cc: mkp.@mkp.net, linux-xfs@oss.sgi.com,
linux-xfs <linux-xfs@thebarn.com>,
linux-kernel@vger.kernel.org
Subject: Re: REPOST : linux-2.5.5-xfs-dj1 - 2.5.7-dj2 (raid0_make_request bug)
Date: Mon, 08 Apr 2002 10:14:48 +0200 [thread overview]
Message-ID: <3CB15178.3020004@st-peter.stw.uni-erlangen.de> (raw)
Hi
>
> 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
>
that helped a lot but i still have two LV's, witch i can not mount
the one complains again about raid0_make_request [lvm(58,1)], but the
other does not [lvm(58,5)]
XFS mounting filesystem lvm(58,5)
Starting XFS recovery on filesystem: lvm(58,5) (dev: 58/5)
XFS: xlog_recover_process_data: bad clientid
XFS: log mount/recovery failed
XFS: log mount failed
XFS mounting filesystem lvm(58,6)
XFS mounting filesystem lvm(58,2)
XFS mounting filesystem lvm(58,3)
XFS mounting filesystem lvm(58,1)
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610013 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610045 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610077 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610109 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610141 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610173 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610205 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23610237 4
I/O error in filesystem ("lvm(58,1)") meta-data dev 0xc03d3a01 block
0xa0210d
("xlog_bread") error 5 buf count 131072
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23611101 4
raid0_make_request bug: can't convert block across chunks or bigger than
16k 23611133 4
I/O error in filesystem ("lvm(58,1)") meta-data dev 0xc03d3a01 block
0xa02565
("xlog_bread") error 5 buf count 30208
XFS: failed to find log head
XFS: log mount/recovery failed
XFS: log mount failed
XFS mounting filesystem lvm(58,4)
next reply other threads:[~2002-04-08 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 8:14 svetljo [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 11:33 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
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=3CB15178.3020004@st-peter.stw.uni-erlangen.de \
--to=galia@st-peter.stw.uni-erlangen.de \
--cc="mkp."@mkp.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®