OK, thanks for the reply. I should have mentioned that I am running SuSE 8.0 and that it has e2fsprogs version 1.26. The comment I quoted is from the 1.26 RELEASE-NOTES, but is dated July 13, 2000. I didn't see anything else in the RELEASE-NOTES that negated it. On Sun, May 12, 2002 at 07:45:13PM -0400, Charles Philip Chan wrote:
On Sun, 12 May 2002 15:48:01 -0500 "Robert C. Paulsen Jr."
wrote: 1. Change /etc/fstab to specify ext3 insterad of ext2.
Yes that is correct.
2. Use tune2fs to add a journal. I think I can do this while the file system is mounted:
tune2fs /dev/sda1 -j
Actually it is
tune2fs -j partition-name
The problem with the journal that is created when the fs is mounted is that it is not hidden (it shows up as a dot file). However, e2fsprog as of 1.27 claims that it will move and hide the journal on the next reboot. In any case I suggest you create the journal on an unmounted fs.
3. Run mkinitrd.
Yes, after you add jbd and ext3 (in that order) to the INITRD_MODULES variable in rc.confg, that is if you are using modules. Also, depending on the version of SuSE that you have, there might be a bug in mkinitrd that prevent ext3 from working proper, I suggest upgrading to the latest just in case.
The above note is dated July 13, 2000. Is this still something to worry about? If so, what can I do about it. Perhaps there is something I can do just before using the dump command, like turning off journaling and/or sync'ing.
You are using an ancient version of e2fsprogs, upgrade immediately if you want to use ext3 (it has much better support for ext3). The version that I am using right now is 1.27 dated Mar 8, 2002.
Charles
-- "If a machine couldn't run a free operating system, we got rid of it."
-- Richard Stallman (Open Sources, 1999 O'Reilly and Associates)
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Robert C. Paulsen, Jr. robert@paulsenonline.net