From: "Stephen C. Tweedie" <sct@redhat.com>
To: Brian Grossman <brian@SoftHome.net>
Cc: linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: ext2: block > big ?
Date: Mon, 12 Feb 2001 15:50:14 +0000 [thread overview]
Message-ID: <20010212155014.A32551@redhat.com> (raw)
In-Reply-To: <20010212004402.3433.qmail@lindy.softhome.net>
In-Reply-To: <20010212004402.3433.qmail@lindy.softhome.net>; from brian@SoftHome.net on Sun, Feb 11, 2001 at 05:44:02PM -0700
Hi,
On Sun, Feb 11, 2001 at 05:44:02PM -0700, Brian Grossman wrote:
>
> What does a message like 'ext2: block > big' indicate?
An attempt was made to access a block beyond the legal max size for an
ext2 file. That probably implies a corrupt inode, because the ext2
file write code checks for that limit and won't attempt to write
beyond the boundary.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
prev parent reply other threads:[~2001-02-12 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 0:44 ext2: block > big ? Brian Grossman
2001-02-12 15:50 ` Stephen C. Tweedie [this message]
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=20010212155014.A32551@redhat.com \
--to=sct@redhat.com \
--cc=brian@SoftHome.net \
--cc=linux-kernel@vger.kernel.org \
/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