public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Tommi Kyntola <kynde@ts.ray.fi>
Cc: Ryan Cumming <bodnar42@phalynx.dhs.org>,
	Patrick Mau <mau@oscar.prima.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.15-pre6 / EXT3 / ls shows '.journal' on root-fs.
Date: Thu, 22 Nov 2001 20:39:10 +0000	[thread overview]
Message-ID: <20011122203910.D11821@redhat.com> (raw)
In-Reply-To: <E165yGL-00012u-00@localhost> <Pine.LNX.4.33.0111200250560.18953-100000@behemoth.ts.ray.fi>
In-Reply-To: <Pine.LNX.4.33.0111200250560.18953-100000@behemoth.ts.ray.fi>; from kynde@ts.ray.fi on Tue, Nov 20, 2001 at 03:20:52AM +0200

Hi,

On Tue, Nov 20, 2001 at 03:20:52AM +0200, Tommi Kyntola wrote:
 
> Minor corrections though, atleast on my 2.4.15-pre6 with tune2fs 1.23
> the .journal is visible even when created as unmounted.

There is absolutely no code in e2fsprogs to create that file on an
unmounted filesystem.  The only mention of the ".journal" name in
e2fsprogs-1.23 is in the code where it opens a regular file with that
name using normal syscalls to access mounted filesystems.  A
".journal" file might be an artifact resulting from doing a recursive
copy from an online-upgraded ext3 filesystem to the new one, though.

> Is the 'rm .journal' the way preferred way to "hide" it?
> Are there any side-effects caused by removal?
> Could someone shed a little more light on this subject.
> What would happen if root were to write to it?

The .journal is an immutable file.  Root will get -EPERM.

> root@behemoth / # tune2fs -O ^has_journal /dev/hda2
> tune2fs 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
> root@behemoth / # mount /tmp
> root@behemoth / # grep /tmp /etc/mtab
> /dev/hda2 /tmp ext2 rw 0 0
> root@behemoth / # umount /tmp
> root@behemoth / # tune2fs -j /dev/hda2
> root@behemoth / # ls -la /tmp | grep journal
> -rw-------    1 root     root      8388608 Oct 23 17:10 .journal

Just clearing the "has_journal" flag from an online-upgraded
filesystem won't be enough to delete the .journal file.  

"dumpe2fs" will tell you what inode the filesystem is actually using
for the journal: I suspect it won't be using that .journal file.

Cheers,
 Stephen

      parent reply	other threads:[~2001-11-22 20:40 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
2001-11-23 19:49               ` Mike Fedyk
2001-11-22 20:39     ` Stephen C. Tweedie [this message]

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=20011122203910.D11821@redhat.com \
    --to=sct@redhat.com \
    --cc=bodnar42@phalynx.dhs.org \
    --cc=kynde@ts.ray.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mau@oscar.prima.de \
    /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