From: Steve Lord <lord@sgi.com>
To: Nico Schottelius <nico-kernel@schottelius.org>, scholz@wdt.de
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bug in 2.6.0test2
Date: 28 Jul 2003 15:47:30 -0500 [thread overview]
Message-ID: <1059425249.6601.10.camel@jen.americas.sgi.com> (raw)
In-Reply-To: <20030728115902.GA18993@schottelius.org>
On Mon, 2003-07-28 at 06:59, Nico Schottelius wrote:
> Hello again!
>
> When trying to boot from a cryptoloop we get the attached error.
> Details:
> modules loop,cryptoloop,aes (in this order) are loaded with insmod
> (from initrd)
> then mounting proc
>
> Any suggestions / solutions ?
>
> Nico
>
> ps: please cc me and scholz AT wdt.de
Something else went wrong before you crashed:
bio too big device loop0 (2 > 0)
This means you cannot use any bio larger than zero to this device,
which is probably why ext2 said this, since it caught the error when
building the bio.
EXT2-fs: unable to read superblock
XFS didn't catch the error building the bio and submitted it, at
which point the I/O tripped the BUG. I can fix this part, but
the original problem is something I know nothing about.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@sgi.com
next prev parent reply other threads:[~2003-07-28 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 11:59 Nico Schottelius
2003-07-28 20:47 ` Steve Lord [this message]
2003-07-28 22:26 ` Nico Schottelius
2003-07-29 11:43 ` Steve Lord
2003-07-29 15:52 ` 2.6.0-test2 usb stack crashed was: " Wiktor Wodecki
2003-07-29 17:40 ` Nico Schottelius
2003-07-31 11:14 ` Nico Schottelius
2003-08-01 17:16 ` Andries Brouwer
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=1059425249.6601.10.camel@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-kernel@schottelius.org \
--cc=scholz@wdt.de \
/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®