From: Andreas Dilger <adilger@clusterfs.com>
To: Thomas Molina <tmolina@cox.net>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: possible partition corruption
Date: Thu, 6 Feb 2003 14:14:15 -0700 [thread overview]
Message-ID: <20030206141415.J18636@schatzie.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.44.0302061501510.998-100000@localhost.localdomain>; from tmolina@cox.net on Thu, Feb 06, 2003 at 03:05:11PM -0600
On Feb 06, 2003 15:05 -0600, Thomas Molina wrote:
> On Thu, 6 Feb 2003, Andrew Morton wrote:
> > Everything you describe is consistent with a kernel which does not have ext3
> > compiled into it.
> >
> > 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.
>
> I'm aware of that. I attached the config file showing ext3 was compiled
> in. I went through several iterations to ensure that having the proper
> filesystem compiled in was done.
Maybe some config/linking breakage puts ext2 in front of ext3 in the probe
order? Try compiling with ext2 as a module.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-02-06 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 20:20 possible partition corruption Thomas Molina
2003-02-06 20:36 ` Andrew Morton
2003-02-06 21:05 ` Thomas Molina
2003-02-06 21:14 ` Andreas Dilger [this message]
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=20030206141415.J18636@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).