-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I created all my ext3 partitions a while back, so the journal.dat file is visable. I'd like to remove them and use the new tune2fs functionality. Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and then remount as ext3? Or am I missing something? thanks! - -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/ ~~ Now offering NO COST Linux admin services for the home user ~~ "That's the problem with science. You've got a bunch of empiricists trying to describe things of unimaginable wonder." -Calvin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjsvbRMACgkQOPP+k4ZeTm2vvwCgj8R44ZKtksYuccy3Yw+PegeJ wxAAnjoUsobwGUPBvZ7Jb5RMTS/LqU6K =oFDa -----END PGP SIGNATURE-----
Hi, On Tue, Jun 19, 2001 at 11:17:39AM -0400, Douglas J. Hunley wrote:> I created all my ext3 partitions a while back, so the journal.dat file is > visable. I'd like to remove them and use the new tune2fs functionality. > Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and > then remount as ext3? Or am I missing something?The easiest way is to clear the HAS_JOURNAL flag on the filesystem with debugfs. Once you do that, e2fsck will detect that the journal record is inconsistent and will fix everything up for you. tune2fs is then able to make you a journal. However, tune2fs will still create a journal file if the filesystem is mounted, so if this is the root filesystem you are talking about, you will still end up with "/.journal" present. tune2fs can only create a completely hidden inode if the filesystem is unmounted at the time. Cheers, Stephen
Douglas J. Hunley writes:> I created all my ext3 partitions a while back, so the journal.dat file is > visable. I'd like to remove them and use the new tune2fs functionality. > Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and > then remount as ext3? Or am I missing something?Your procedure is mostly correct. You need to unmount the filesystem and run e2fsck on it before running tune2fs if you want a hidden journal. If you can't unmount the filesystem, you can easily rename journal.dat to .journal (this is what tune2fs calls it if it is created on a mounted fs). It is safe because ext3 accesses the journal by inode number and not name. You may also have to turn off the immutable flag (chattr -i journal.dat) if you are deleting it. Note that recent versions of ext2 dump (0.4b21 I think) check for a journal inode number and do not dump it. I don't know if GNU tar checks the nodump file attribute or not, so the journal in reserved inode 8 is safest. Cheers, Andreas -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert