From: Andreas Dilger <adilger@turbolabs.com>
To: Ben Collins <bcollins@debian.org>
Cc: Andrew Morton <akpm@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Bug in ext3
Date: Thu, 15 Nov 2001 14:58:03 -0700 [thread overview]
Message-ID: <20011115145803.R5739@lynx.no> (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
On Nov 15, 2001 16:02 -0500, Ben Collins wrote:
> On Thu, Nov 15, 2001 at 12:48:26PM -0800, Andrew Morton wrote:
> > ext3 thinks that the filesystem's superblock has the
> > EXT3_FEATURE_COMPAT_HAS_JOURNAL bit set in the s_feature_compat
> > field of the on-disk superblock.
> >
> > It's probable that that bit _is_ set. ext2 will never notice it.
> >
> > Please: the dumpe2fs output?
>
> 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.
> Is there any reason to mount a partition as ext3 if there is no journal
> to be found?
It _does_ fail to mount the filesystem as ext3, and the ext2 code properly
mounts it. You can see this because the error message you got (in your
previous posting said "EXT2-fs: ..." so the error came from ext2.
Please run e2fsck (1.25) to clear this up. It may be that you have other
corruption in your filesystem. If you are sure you _never_ tried ext3
on this filesystem before, yet the has_journal bit is set, this could
be an indication of memory or cable problems.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-15 22:00 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 [this message]
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
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=20011115145803.R5739@lynx.no \
--to=adilger@turbolabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox