public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Cumming <bodnar42@phalynx.dhs.org>
To: Patrick Mau <mau@oscar.prima.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.15-pre6 / EXT3 / ls shows '.journal' on root-fs.
Date: Mon, 19 Nov 2001 15:55:40 -0800	[thread overview]
Message-ID: <E165yGL-00012u-00@localhost> (raw)
In-Reply-To: <20011120004350.A9631@oscar.dorf.de>
In-Reply-To: <20011120004350.A9631@oscar.dorf.de>

On November 19, 2001 15:43, Patrick Mau wrote:
> Hallo all,
>
> I'm using kernel 2.4.15-pre6 and I can see my journal file
> on '/'. Should I worry ?
No, apparently the .journal file is visible if you created while the 
filesystem is mounted, but invisible if you create it when the filesystem is 
unmounted. Probably because you can't mess with the filesystem too much when 
its mounted without confusing the filesystem driver, so creating hidden files 
is out of the question. In either case, I created my journal with the 
filesystem mounted, and it created a visible, immutable .journal file in my 
root directory, and my filesystem has yet to explode.

> [root@tony] ls -ali /
> total 65720
>    2 drwxr-xr-x   24 root     root         4096 Nov 20 00:26 .
>    2 drwxr-xr-x   24 root     root         4096 Nov 20 00:26 ..
> 2930 -rw-------    1 root     root     67108864 Nov 18 19:56 .journal
> 					^^^^^^^ created as -J size=64
64 * (1024^2) = 67108864
Remember 1K = 1024, and 1M = 1024^2

>
> [root@tony] tune2fs -l /dev/sda1
> tune2fs 1.25 (20-Sep-2001)
> Filesystem volume name:   /
> Last mounted on:          <not available>
> Filesystem UUID:          b909b36d-8f16-4be1-9614-5049bad90e96
> Filesystem magic number:  0xEF53
> Filesystem revision #:    1 (dynamic)
> Filesystem features:      has_journal filetype needs_recovery sparse_super
>                                                ^^^^^^^^^^^^^^
> 					       ??????????????
The flag "filetype needs_recovery" is always set on a mounted filesystem, 
it's unset once you umount. In the event of power failure, the flag will be 
left set, and fsck knows the it has to recover the filesytem. Pretty clever, 
eh?

> Could someone please comment on this ?
> I'm feeling kind of worried.
Everything seems to be in order...

-Ryan

  reply	other threads:[~2001-11-19 23:56 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 [this message]
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

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=E165yGL-00012u-00@localhost \
    --to=bodnar42@phalynx.dhs.org \
    --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