All of lore.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <E166pXF-0000mm-00@Princess> (raw)
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>

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...

  reply	other threads:[~2001-11-22  8:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 23:43 Kernel 2.4.15-pre6 / EXT3 / ls shows '.journal' on root-fs Patrick Mau
2001-11-19 23:55 ` Ryan Cumming
2001-11-20  1:20   ` Tommi Kyntola
2001-11-20  1:28     ` Ryan Cumming
2001-11-20  1:37       ` Tommi Kyntola
2001-11-20  1:41         ` Rik van Riel
2001-11-20  1:48           ` Tommi Kyntola
2001-11-20  3:43             ` Mike Castle
2001-11-20  3:46               ` Ryan Cumming
2001-11-20  4:05                 ` Mike Castle
2001-11-20  4:14                   ` Ryan Cumming
2001-11-22 20:41                   ` Stephen C. Tweedie
2001-11-20  1:55         ` Ryan Cumming
2001-11-20 19:19           ` Andreas Dilger
2001-11-22  8:48             ` Allan Sandfeld [this message]
2001-11-23 19:49               ` Mike Fedyk
2001-11-22 20:39     ` Stephen C. Tweedie

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=E166pXF-0000mm-00@Princess \
    --to=linux@sneulv.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.