Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S281087AbRKVIuY>; Thu, 22 Nov 2001 03:50:24 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S281126AbRKVIuO>; Thu, 22 Nov 2001 03:50:14 -0500
Received: from [213.237.118.153] ([213.237.118.153]:6784 "EHLO Princess")
	by vger.kernel.org with ESMTP id <S281087AbRKVIuD>;
	Thu, 22 Nov 2001 03:50:03 -0500
Content-Type: text/plain; charset=US-ASCII
From: Allan Sandfeld <linux@sneulv.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.15-pre6 / EXT3 / ls shows '.journal' on root-fs.
Date: Thu, 22 Nov 2001 09:48:37 +0100
X-Mailer: KMail [version 1.3.2]
In-Reply-To: <Pine.LNX.4.33.0111200328550.842-100000@behemoth.ts.ray.fi> <E16608e-0001CL-00@localhost> <20011120121947.V1308@lynx.no>
In-Reply-To: <20011120121947.V1308@lynx.no>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Message-Id: <E166pXF-0000mm-00@Princess>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Tuesday 20 November 2001 20:19, Andreas Dilger wrote:
> On Nov 19, 2001  17:55 -0800, Ryan Cumming wrote:
> > On November 19, 2001 17:37, you wrote:
> > > Even so, I'm wondering wether this removal is standardad
> > > procedure for hiding it once and for all or not?
>
> Very definitely NOT.  It _may_ work until the filesystem is unmounted,
> because the kernel will keep the file "open" so that the inode is not
> freed, but the next time you try to mount the filesystem it will
> complain about the journal being a bad inode.
>
> > On my system, the journal appears to have a perfectly normal inode number
> > for a root entry (#22), which makes me think that it's just a normal file
> > as far as the core filesystem code is concerned.
>
> Correct.  Normal, except that if you (as root) really work hard to fool
> with it, you can potentially cause problems.  Don't do that.  The problems
> are 99.99% harmless - can't mount as ext3, e2fsck will complain, maybe you
> can't boot your system, if it is the root fs.  If you really work at it,
> maybe you can corrupt your fs, but that would take serious effort plus a
> crash.
>
I just tried this... :)

First corrupted .journal is reported, then "journal deleted, mounting as 
ext2-only" followed by a forced e2fsck.

Thats what I call a well handled error...
-
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/