Date: Tue, 16 Mar 2004 02:43:09 -0800
From: Andrew Morton <akpm@osdl.org>
To: Kristian Soerensen <ks@cs.auc.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] Recovering ext3 - recovery.c: assertion failed,
 attempted to kill init
Message-Id: <20040316024309.53da4f50.akpm@osdl.org>
In-Reply-To: <1079430906.19929.10.camel@homer.cs.auc.dk>
References: <1079430906.19929.10.camel@homer.cs.auc.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1131
Lines: 34

Kristian Soerensen <ks@cs.auc.dk> wrote:
>
> After (hard) power cycling a computer, running linux-2.6.3*, the
>  filsystem (ext3) sould be recovered at boot. However I get the following
>  message from the kernel. I have tried booting the redhat
>  kernel-2.4.20-30.9 - but with the same result.
> 
>  * The kernel was patched with our Umbrella LSM module, but however _no_
>  changes were made to the filesystem.
> 
> ...
> 
>  Assertion failure in jread() at fs/jbd/recovery.c:140: "offset <
>  journal->j_maxlen"

A wrecked journal superblock or log block.  Never seen that before.

See if e2fsck can fix it up.  If not, see if you can get e2fsck to remove
the journal with

	tune2fs -O ^has_journal /dev/hdXX

then fsck it, then create a new journal with

	tune2fs -j /dev/hdXX

As for the assertion failure: yes, that's fairly bad form.  I'll fix that
up to simply fail the mount.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/