From: "Marcel J.E. Mol" <marcel@mesa.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Moving ext3 journal file
Date: Sat, 24 Nov 2001 11:54:11 +0100 [thread overview]
Message-ID: <20011124115411.C25094@joshua.mesa.nl> (raw)
In-Reply-To: <E167Fuw-00001K-00@DervishD> <Pine.LNX.4.33.0111231944430.2891-100000@fargo> <20011123155901.C1308@lynx.no> <9tmocg$jfn$1@cesium.transmeta.com>
In-Reply-To: <9tmocg$jfn$1@cesium.transmeta.com>; from hpa@zytor.com on Fri, Nov 23, 2001 at 04:07:44PM -0800
On Fri, Nov 23, 2001 at 04:07:44PM -0800, H. Peter Anvin wrote:
> Followup to: <20011123155901.C1308@lynx.no>
> By author: Andreas Dilger <adilger@turbolabs.com>
> In newsgroup: linux.dev.kernel
> >
> > Don't do that. That is only good if the filesystem thinks that there
> > is no journal, or it is using a hidden inode for the journal (i.e. if
> > you run "tune2fs -l /dev/whatever" and it doesn't have "has_journal"
> > listed in the filesystem features (this is what happened with 2.4.10).
> > Otherwise, you will delete your real journal, tune2fs will complain,
> > and then you will need to run e2fsck to clean up after yourself, before
> > re-creating your journal again.
> >
> > If you have a filesystem with a .journal file, and you want to "hide"
> > it, just run e2fsck 1.25 while the filesystem is unmounted, and it
> > will do it for you. If you don't want to have a .journal in the first
> > place, run tune2fs -j while the filesystem is unmounted.
> >
>
> This is all fine and good except for the root partition (I'm pleased
> to hear that e2fsck 1.25 will move the journal to the hidden inode for
> non-root partitions.) It would be nice if this was done automagically
> by the mounting code instead of by fsck; that way migration would
> truly be painless.
Hm, the e2fsck check does not work for me...
The .journal file still exists after
# umount /dev/hda11
# e2fsck -f /dev/hda11
# mount /dev/hda11
# rpm -q e2fsprogs
e2fsprogs-1.25-1
(on redhat rawhide)
-Marcel
--
======-------- Marcel J.E. Mol MESA Consulting B.V.
=======--------- ph. +31-(0)6-54724868 P.O. Box 112
=======--------- marcel@mesa.nl 2630 AC Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
They couldn't think of a number, Linux user 1148 -- counter.li.org
so they gave me a name! -- Rupert Hine -- www.ruperthine.com
next prev parent reply other threads:[~2001-11-24 10:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 12:58 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
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 [this message]
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=20011124115411.C25094@joshua.mesa.nl \
--to=marcel@mesa.nl \
--cc=hpa@zytor.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
all inboxes | Powered by JetHome®