From: Andrew Morton <akpm@digeo.com>
To: Wil Reichert <wilreichert@yahoo.com>, Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "bio too big" error
Date: Tue, 10 Dec 2002 18:44:03 -0800 [thread overview]
Message-ID: <3DF6A673.D406BC7F@digeo.com> (raw)
In-Reply-To: 1039572597.459.82.camel@darwin
Wil Reichert wrote:
>
> Hi,
>
> I'm getting a "bio too big" error with 2.5.50. I've got a 330G lvm2
> partition formatted with ext3 using the -T largefile4 parameter.
> Everything seems ok at first, but any sort of access will die very
> unhappily with said error messsage after about 10 seconds of operation
> or so. The only google search results are the patch submission. Eeek.
>
How odd.
Please send the full diagnostic output.
And add this:
--- 25/drivers/block/ll_rw_blk.c~a Tue Dec 10 18:42:54 2002
+++ 25-akpm/drivers/block/ll_rw_blk.c Tue Dec 10 18:43:13 2002
@@ -1921,6 +1921,7 @@ end_io:
bdevname(bio->bi_bdev),
bio_sectors(bio),
q->max_sectors);
+ dump_stack();
goto end_io;
}
_
next prev parent reply other threads:[~2002-12-11 2:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 2:17 "bio too big" error Wil Reichert
2002-12-11 2:44 ` Andrew Morton [this message]
2002-12-11 3:38 ` Wil Reichert
2002-12-11 5:11 ` Greg KH
2002-12-11 13:40 ` Wil Reichert
2002-12-11 19:16 ` Greg KH
2002-12-11 5:18 ` Andrew Morton
2002-12-11 12:09 ` Wil Reichert
2002-12-11 7:21 ` Jens Axboe
2002-12-12 9:22 ` Joe Thornber
2002-12-12 12:08 ` Joe Thornber
2002-12-12 18:34 ` Wil Reichert
2002-12-12 20:29 ` Joe Thornber
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 23:45 Confusing help texts? Greg KH
2002-12-12 0:15 ` "bio too big" error Wil Reichert
2002-12-12 9:12 ` Joe Thornber
2002-12-12 17:33 ` Wil Reichert
2002-12-12 21:51 ` Kevin Corry
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=3DF6A673.D406BC7F@digeo.com \
--to=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wilreichert@yahoo.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