public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Michael Zimmermann <zim@vegaa.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Andreas Dilger <adilger@turbolabs.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Moving ext3 journal file
Date: Sun, 25 Nov 2001 02:33:14 -0800	[thread overview]
Message-ID: <20011125023314.B30336@mikef-linux.matchmail.com> (raw)
In-Reply-To: <E167Fuw-00001K-00@DervishD> <20011123155901.C1308@lynx.no> <9tmocg$jfn$1@cesium.transmeta.com> <20011123174120.Q1308@lynx.no> <9tmr83$jo2$1@cesium.transmeta.com> <20011123212557.U1308@lynx.no> <3BFF2AAE.7000000@zytor.com> <3BFF8692.7060900@vegaa.de>
In-Reply-To: <3BFF8692.7060900@vegaa.de>

On Sat, Nov 24, 2001 at 12:37:54PM +0100, Michael Zimmermann wrote:
> Excuse me, if I jump in with almost zero linux-kernel-knowledge,
> and take my words as a third-party comment.
> 
> May be, I've not seen enough in 35 years of system programming
> (including designing and writing journal-systems my own),
> but I've never seen a journal beeing part of the data-space to be
> journalled. It is simply an ugly thing in the file space. It either belongs
> into /proc/fs/ext3 (or the like) or is not to be shown at all. Except
> there was a valid neccessity to have it in the normal file space.
> 

You do not understand the reasons behind the thread.

.journal files are only created when an ext2 FS is converted to ext3 *while*
it is mounted.  In this case tune2fs just creates a file (.journal) and
modifies a couple fields in the super block.

The newest e2fsck (1.25) will hide the file for you, just like it would be
if the conversion was done on an unmounted FS.

MF

  reply	other threads:[~2001-11-25 10:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 12:58 Moving ext3 journal file RaúlNúñez de Arenas Coronado
2001-11-23 18:20 ` Andreas Dilger
2001-11-24  1:02 ` David Gómez 
2001-11-23 22:59   ` Andreas Dilger
2001-11-24  0:07     ` H. Peter Anvin
2001-11-24  0:41       ` Andreas Dilger
2001-11-24  0:56         ` H. Peter Anvin
2001-11-24  4:25           ` Andreas Dilger
2001-11-24  5:05             ` H. Peter Anvin
2001-11-24 11:37               ` Michael Zimmermann
2001-11-25 10:33                 ` Mike Fedyk [this message]
2001-11-25 11:14                   ` Mike Castle
2001-11-25 22:55                     ` Mike Fedyk
2001-11-25 23:55                       ` Mike Fedyk
2001-11-24 17:26               ` Jamie Lokier
2001-11-24 17:49               ` Thorsten Glaser
2001-11-24 10:54       ` Marcel J.E. Mol
2001-11-24 21:19         ` Mike Castle
2001-11-24 22:49           ` Andreas Dilger
2001-11-25  3:34             ` Mike Castle

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=20011125023314.B30336@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=adilger@turbolabs.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zim@vegaa.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