From: Andrew Morton <akpm@digeo.com>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible partition corruption
Date: Thu, 6 Feb 2003 12:36:31 -0800 [thread overview]
Message-ID: <20030206123631.617524f7.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302061351380.998-200000@localhost.localdomain>
Thomas Molina <tmolina@cox.net> wrote:
>
> I have run into an apparent anomaly while compiling/testing 2.5.59-bk. My
> normal mode of operation is to do a daily bk pull to get the latest csets
> and do a compile/boot run. After yesterday's I started seeing problems on
> reboot. During the reboot I would get the OK booting the kernel followed
> by a system freeze. After a forced reboot into a stock RedHat 8.0 2.4
> kernel I would see the system misidentify my boot partiton as an ext2
> partition and the following messages would appear:
>
Everything you describe is consistent with a kernel which does not have ext3
compiled into it.
> EXT2-fs: ide0(3,8): couldn't mount because of unsupported optional feature
> (4).
> Kernel panic: VFS: Unable to mount root fs on 08:08
>
That is an ext3 filesystem in the "needs journal recovery" state. ext2
cannot mount that until either fsck or the ext3 kernel driver has run
recovery.
grep EXT3 .config ??
next prev parent reply other threads:[~2003-02-06 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 20:20 Thomas Molina
2003-02-06 20:36 ` Andrew Morton [this message]
2003-02-06 21:05 ` Thomas Molina
2003-02-06 21:14 ` Andreas Dilger
2003-02-06 22:35 ` Thomas Molina
2003-02-06 21:23 ` Andrew Morton
2003-02-06 21:33 ` Thomas Molina
2003-02-06 21:40 ` Andrew Morton
[not found] <Pine.LNX.4.44.0302061848360.851-200000@localhost.localdomain>
2003-02-07 19:59 ` Thomas Molina
2003-02-07 22:15 ` Andrew Morton
2003-02-07 23:54 ` Thomas Molina
2003-02-07 23:40 ` Andrew Morton
2003-02-08 1:48 ` Thomas Molina
2003-02-08 2:06 ` Andrew Morton
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=20030206123631.617524f7.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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®