From: Mike Castle <dalgoda@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Moving ext3 journal file
Date: Sat, 24 Nov 2001 13:19:02 -0800 [thread overview]
Message-ID: <20011124131902.A537@thune.mrc-home.com> (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> <20011124115411.C25094@joshua.mesa.nl>
In-Reply-To: <20011124115411.C25094@joshua.mesa.nl>
On Sat, Nov 24, 2001 at 11:54:11AM +0100, Marcel J.E. Mol wrote:
> On Fri, Nov 23, 2001 at 04:07:44PM -0800, H. Peter Anvin wrote:
> > 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
I was just going to comment on this as well. I cannot get this to work as
advertised on a homegrown system as well.
Even tune2fs -l | grep inode and ls -i .journal show it's still using the
same inode.
Actually, a quick look through the code, I can't see where e2fsck would
take measures to hide .journal. At least not in 1.25.
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
next prev parent reply other threads:[~2001-11-24 21:19 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
2001-11-24 21:19 ` Mike Castle [this message]
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=20011124131902.A537@thune.mrc-home.com \
--to=dalgoda@ix.netcom.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®