Re: Moving ext3 journal file
Andreas Dilger (firstname.lastname@example.org)
Fri, 23 Nov 2001 17:41:20 -0700
On Nov 23, 2001 16:07 -0800, H. Peter Anvin wrote:
> By author: Andreas Dilger <email@example.com>
> > 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.
Hmm, it could be added into the in-kernel ext3 journal recovery code, maybe,
possibly, but it would be ugly I think. I really don't see it as being a
problem (other than a purely cosmetic one) to have a .journal file in your
root fs. I lived with these for a couple of years OK (even some of the
early ext3 tools called them "journal.dat" (i.e. not a leading dot, ugh).
In 2.5 it would be easy (and preferrable for other reasons) to have e2fsck
run from the initramfs on the root fs before it is mounted. That solves
the problem nicely without adding bloat into the kernel. We could even
remove the in-kernel journal recovery at that point if we thought that the
initramfs was a reliable environment to host _critical_ boot tools.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/