mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Campbell <campbell@accelinc.com>
To: "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.2 kernel and ext3 filesystems
Date: Wed, 28 Jan 2004 14:58:10 -0600	[thread overview]
Message-ID: <20040128205810.GA8287@helium.inexs.com> (raw)
In-Reply-To: <20040127012717.GA19704@thunk.org>

On Mon, Jan 26, 2004 at 08:27:17PM -0500, Theodore Ts'o wrote:
> 
> There were also some bug fixes that I'm pretty sure were never
> backported into the 2.2 tree....

I may be being stung by this as we speak.

I mounted this ext3 filesystem as ext2 on my 2.2.16 kernel system. I made 
some changes to some files (simple edits), and now when I reboot the box in
2.2.16, I get the following:

mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
       or too many mounted filesystems

in /var/log/messages I see:
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs: ide0(3,66): couldn't mount because of unsupported optional features.


I'm reticent to run any e2fsck as old as 2.2.16 kernel version against
this filesystem, in fear of damaging it.  Is this a sane thing to consider,
or do I need to put this disk back into a more recent box and try to mount it/
fsck it there?

Alternatively, where might I dig up an ext3 patch against linux-2.2.x, so
I can build a kernel that will support this?  I assume I would need file
utilities that support it as well?

thanks,
-chuck


-- 

  reply	other threads:[~2004-01-28 20:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24  3:32 Chuck Campbell
2004-01-24  5:58 ` Andrew Morton
2004-01-26 14:56   ` Chuck Campbell
2004-01-26 19:04     ` Andre Tomt
2004-01-26 20:41     ` Andrew Morton
2004-01-27  1:27       ` Theodore Ts'o
2004-01-28 20:58         ` Chuck Campbell [this message]
2004-01-28 21:28           ` Andreas Dilger

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=20040128205810.GA8287@helium.inexs.com \
    --to=campbell@accelinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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®