Tener, Stuart B., IT3 , USNR-R
2002-Jul-06 20:34 UTC
Changing journaling mode on root / loop-aes
EXT3 developers: I am curious, if EXT3 is currently being used on the root partition in "data=ordered" mode (the default as I understand), and I want to have the it come up in data=journal mode, how do you effectuate this conversion? I would also be curious how to know if anything special is required for doing so for the /boot partition as well. I believe that with the /home partition, all it required was unmounting and remounting with the new option in /etc/fstab. Do I have to boot up in rescue mode with a CD and do something to make the root partition have a different journal? While this is not really an EXT3 question, I am sure people here might have knowledge to answer it anyway. Currently both Mandrake and SuSE have an encrypted filesystem implementation using loop backed devices (which I think even allow the /boot and root partitions to be encrypted as well using inird images). I am curious if there is intent on the part of RedHat to support an encryption mechanism? I ask this as I am talking to someone from the Navy Reserves about how and if we can use RedHat for a project we are talking about. He leans toward using SuSE since it has encryption, where I prefer RedHat for other reasons. Will we ever see such support in RedHat? Very Respectfully, Stuart Blake Tener, IT3 (E-4), USNR-R, N3GWG Beverly Hills, California VTU 1904G (Volunteer Training Unit) stuart@bh90210.net west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. Saturday, July 06, 2002 1:33 PM
On Sat, 6 Jul 2002, Tener, Stuart B., IT3 , USNR-R wrote:> EXT3 developers: > > I am curious, if EXT3 is currently being used on the root > partition in "data=ordered" mode (the default as I understand), and I > want to have the it come up in data=journal mode, how do you effectuate > this conversion? I would also be curious how to know if anything special > is required for doing so for the /boot partition as well. I believe that > with the /home partition, all it required was unmounting and remounting > with the new option in /etc/fstab. > > Do I have to boot up in rescue mode with a CD and do something > to make the root partition have a different journal? >Add this to the linux boot section in lilo.conf: append="rootflags=data=journal" and to options in fstab "data=journal"
Tener, Stuart B., IT3 , USNR-R
2002-Jul-08 18:40 UTC
Re: Changing journaling mode on root / loop-aes
List members: I have now performed and analyzed the following things, and am still not able to boot with root in data=journal mode. (a) It ought be pointed out that before I tried to get the root to be able to boot up using data=journal logging, I was had an EXT3 root, and did boot fine in its default mode (which I understand is not data=journal mode) (b) I also checked using /proc/mount, and it yielded far less useful information than typing mount. It did show that all the partitions were in fact mounted as "EXT3", even root. (c) I then made sure that /etc/fstab had the "data=journal" option in the root partition entry. Then I verified that "rootflags=data=journal" was placed in the /etc/grub/grub.conf file properly, and rebooted. However, the same result occurred the "03:06" boot error...AGAIN!?! ARGH!!! I am not trying to call into question the integrity of EXT3, but this does not seem to work. And I must admit I am curious why the root partition cannot be made to operate in data=journal mode just because I choose to use an initrd? Very Respectfully, Stuart Blake Tener, IT3 (E-4), USNR-R, N3GWG Beverly Hills, California VTU 1904G (Volunteer Training Unit) stuart@bh90210.net west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. Monday, July 08, 2002 11:34 AM
On Mon, Jul 08, 2002 at 11:40:26AM -0700, Tener, Stuart B., IT3 , USNR-R wrote:> (c) I then made sure that /etc/fstab had the "data=journal" > option in the root partition entry. Then I verified that > "rootflags=data=journal" was placed in the /etc/grub/grub.conf file > properly, and rebooted. However, the same result occurred the "03:06" > boot error...AGAIN!?! ARGH!!!Sorry to join this party late, but .... You say elsewhere in this thread that you are using a RH7.3ish system with an initrd. But the rootflags=data=journal flag is only for use when ext3 is compiled into the kernel. [Someday Rusty Russell will unify param handling, $DEITY willing.] When using an initrd with the ext3 and jbd modules, you need to place the appropriate options in /etc/fstab, and remake the initrd. Caveat: the version of mkinitrd that shipped with RH7.3 does not do this automatically. In fact, it was added on 2002/05/21 by Erik Troan: * Tue May 21 2002 Erik Troan <ewt@redhat.com> - use options from fstab for root filesystem (56071) [Courtesy of "rpm -q --changelog mkinitrd" on my box.] The number in parentheses is the bugzilla number; see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=56071 So what you have to do is go to Rawhide and grab a recent mkinitrd, install it with rpm -Uvh mkinitrd-*.i386.rpm, then rebuild your initrd. Something like: rpm -Uvh mkinitrd-3.4.12.i386.rpm cp /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.sav mkinitrd -v /boot/initrd-`uname -r`.img `uname -r` and reboot. Regards, Bill Rugolsky