From: Andreas Dilger <adilger@turbolabs.com>
To: "RaúlNúñez de Arenas Coronado" <dervishd@jazzfree.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Moving ext3 journal file
Date: Fri, 23 Nov 2001 11:20:09 -0700 [thread overview]
Message-ID: <20011123112009.V1308@lynx.no> (raw)
In-Reply-To: <E167Fuw-00001K-00@DervishD>
In-Reply-To: <E167Fuw-00001K-00@DervishD>; from dervishd@jazzfree.com on Fri, Nov 23, 2001 at 01:58:54PM +0100
On Nov 23, 2001 13:58 +0100, RaúlNúñez de Arenas Coronado wrote:
> Is there any problem on moving the /.journal file (even renaming
> it) so it doesn't lives on the root? I mean, maintaining its inode
> number, of course ;))
The name is irrelevant. The kernel only accesses the journal by inode
number, and only once at boot time. Rather than "renaming" it and
causing problems, you should just unmount the filesystem, and run
"e2fsck -f /dev/hdX" (with e2fsck 1.25) and it will hide it for you.
> Anyway, ext3 shouldn't (just an idea) show the journal as a
> normal file. It may add some load on the kernel, because the inode
> number should be compared with that of the journal every time a file
> is accessed, but it's just a suggestion ;))
???? This doesn't make sense. Having the .journal file places no load
on the system. OK, when you do "ls -a /" it has to list an extra file,
but that is so little work as to be unnoticable. Even with a hidden
journal, it is still in an inode with an inode number, it's just not
in a directory anywhere.
As to "comparing the inode number to that of the journal every time a
file is accessed" it appears you just don't understand how file access
works in the kernel.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-23 18:20 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 [this message]
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
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=20011123112009.V1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=dervishd@jazzfree.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox