From: "Stephen C. Tweedie" <sct@redhat.com>
To: Ben Collins <bcollins@debian.org>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: Bug in ext3
Date: Fri, 16 Nov 2001 14:52:31 +0000 [thread overview]
Message-ID: <20011116145231.A6528@redhat.com> (raw)
In-Reply-To: <20011115092452.Z329@visi.net> <3BF3F9ED.17D55B35@zip.com.au>, <3BF3F9ED.17D55B35@zip.com.au> <20011115153442.A329@visi.net> <3BF42A1A.5AE96A78@zip.com.au> <20011115160232.H329@visi.net>
In-Reply-To: <20011115160232.H329@visi.net>; from bcollins@debian.org on Thu, Nov 15, 2001 at 04:02:32PM -0500
Hi,
On Thu, Nov 15, 2001 at 04:02:32PM -0500, Ben Collins wrote:
>
> Seems it does have the field set. I guess the bug is then that if there
> is no journal, then it shoudl fail to mount it, so ext2 will take over.
It _did_ fail to mount it, and ext2 _did_ take over: that's why, when
ext2 found something else wrong with the filesystem, the errors
looked like
EXT2-fs error (device sd(8,20)): ext2_free_blocks: Freeing blocks not
in datazone - block = 4294965248, count = 6872
which were marked as ext2 warnings, not ext3 warnings.
Cheers,
Stephen
prev parent reply other threads:[~2001-11-16 14:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 14:24 Bug in ext3 Ben Collins
2001-11-15 17:22 ` Andrew Morton
2001-11-15 20:34 ` Ben Collins
2001-11-15 20:48 ` Andrew Morton
2001-11-15 21:02 ` Ben Collins
2001-11-15 21:10 ` Andrew Morton
2001-11-15 22:04 ` Ben Collins
2001-11-15 21:58 ` Andreas Dilger
2001-11-15 22:06 ` Ben Collins
2001-11-15 22:49 ` Mike Fedyk
2001-11-15 22:58 ` Ben Collins
2001-11-15 23:21 ` Andreas Dilger
2001-11-15 23:38 ` Ben Collins
2001-11-16 0:07 ` Andreas Dilger
2001-11-16 0:55 ` Ben Collins
2001-11-16 3:09 ` Andreas Dilger
2001-11-16 3:20 ` Ben Collins
2001-11-16 3:37 ` Mike Fedyk
2001-11-16 4:50 ` Andreas Dilger
2001-11-16 18:38 ` Stephen C. Tweedie
2001-11-16 18:44 ` Stephen C. Tweedie
2001-11-16 14:52 ` 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=20011116145231.A6528@redhat.com \
--to=sct@redhat.com \
--cc=akpm@zip.com.au \
--cc=bcollins@debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.