From: "Marco C. Mason" <mason@ntr.net>
To: linux-kernel@vger.kernel.org, raid@a2000.nu
Subject: fsck out of memory
Date: Mon, 10 Feb 2003 21:53:10 -0500 [thread overview]
Message-ID: <3E486596.2090800@ntr.net> (raw)
Stephan--
I don't know if anyone mentioned it or not, but the block addresses in your
error messages appear suspiciously close to 2^29. I'm suspecting an
internal
overflow in a calculation somewhere...
--marco
next reply other threads:[~2003-02-11 2:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 2:53 Marco C. Mason [this message]
2003-02-11 15:32 ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
[not found] <Pine.LNX.4.33.0302071637050.11484-100000@nooks.wimpunk.com>
2003-02-07 15:50 ` fsck out of memory kernel
2003-02-07 16:09 ` Wim Vinckier
2003-02-07 16:15 ` Stephan van Hienen
2003-02-07 16:20 ` Wim Vinckier
2003-02-07 17:08 ` Stephan van Hienen
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 15:17 kernel
2003-02-07 17:07 ` Stephan van Hienen
2003-02-07 17:28 ` Andreas Dilger
2003-02-09 10:08 ` Stephan van Hienen
2003-02-09 10:32 ` Stephan van Hienen
2003-02-09 20:08 ` Peter Chubb
2003-02-10 11:28 ` Stephan van Hienen
2003-02-09 20:31 ` Andreas Dilger
2003-02-10 12:01 ` Stephan van Hienen
2003-02-07 17:24 ` Andreas Dilger
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=3E486596.2090800@ntr.net \
--to=mason@ntr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=raid@a2000.nu \
/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