similar to: rootflags=data=journal and grub

Hi All, I'm new to ext3 and I'd like to boot in data=journal mode. I'm running the latest Debian stable. Where do I put this directive so it happens on every reboot? In the "append=" line in /etc/lilo.conf? Sorry for the confusion, but this line isn't clear to me: ------------------------ You may provide mount options to the root filesystem via LILO using the rootflags

I tried to convert / to ext3, so I went ahead and entered rootflags=noload,journal=355 on the LILO prompt. The kernel failed to mount /: EXT3-fs error (device ramdisk(1,0)): ext3_get_inode_loc: bad inode number: 355 The boot device is a scsi hard disk, so initrd is used to load the scsi driver, before mounting /. So, it looks like the kernel rootflags= arg gets applied to the ramdisk, not the

I am using RedHat 7.2 w/ kernel 2.4.7-10. My / filesystem is configured as ext3. I want to change it to use data=journaled instead of ordered. If I mount it from a boot floppy, it mounts fine. (mount /dev/hda2 /mnt -t ext3 -o data=journal). I have attempted to find the correct procedure to start it up as journaled from grub to no avail. I have created a new initrd image that works fine with

Hi Thomas, >----Messaggio originale---- >Da: thomas@kupper.org >Data: 22/01/2010 10.48 >A: "Leszek Ciesielski"<skolima@gmail.com> >Cc: "linux-btrfs"<linux-btrfs@vger.kernel.org> >Ogg: Re: mount command not honoring rootflags passed > > >On 22 Jan 2010, at 10:40, Leszek Ciesielski wrote: > >> On Fri, Jan 22, 2010 at 10:30 AM,

Hi all, On my slackware 7.1 system, in rc.S fsck is started. In fstab there's the following line: /dev/hda2 / ext3 defaults,noatime 1 1 from the readme I figured that I should put the line append="rw rootflags=journal=102" in lilo.conf The system boots up, but I get the error message that the root partition is already rw. Should I just skip the filesystem

Doing some debugging of my kernel build with ext3 and noticed something interesting. At the bottom of the rootflags options processing loop there is a return failure if there was an option that ext3 did not know about. Should this be the behaviour? Would it not be better to ignore options not recognized? Surely, some day, some other filesystem is going to want to use rootflags to have one of

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

I updated my kernel from 0.0.3d to 0.0.3e using the "d-e" patch in the 0.0.3e tarball. When I try to boot the new kernel on a machine with an ext3 root filesystem I am getting the message: JFS: Unrecognised features on journal Does this sound feasible or even somewhat expected? Is there any interest in me doing some debugging of this? Is there any way to deal with this without

Hi all, I've been working with the ext3-fs for several months (since 0.0.2c), and it works pretty fine for me, but I haven't found out, how I works to migrate my root-partition from ext2 to ext3. I tried it with the commands at the lilo-prompt, but it didn't work. I only received a kernel panic. Any ideas, how I can migrate to ext3 on my root-partition? tnx, Joachim -- Joachim

Hi, I'm running 2.4.9-ac7 with ext3 compiled in, and I ran across this problem. Now that I look back, it makes sence, but it wasn't obvious at first... I wanted to change the journal mode on my / partition, so I changed my fstab to: /dev/hda1 / ext3 defaults,errors=remount-ro,data=journal 0 1 as well as several other partitions, and rebooted. After rebooting I had a read only / that I

My guinea pig laptop has only a / partition, and a small /boot partition. I installed the ext3 kernel succesfully (I think). Now, how do I get / converted to ext3? I'm thinking: * Use mkbootdisk on a floppy, to create a boot disk with the ext3 kernel. * Boot off the floppy. * Follow the instructions to convert / to ext3. * Change the filesystem type in /etc/fstab to ext3. * Reboot.

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,

I am trying to use data=journal on my root file system. I have separate slices on which journal=data works fine on all of them, except root. I have tried putting rootflags=journal=data on my kernel line in Grub, but I get a kernel panic. I'm missing something simple, I jut know it. It can't be the kernel version because it works on the other slices. My etc/fstab file is as follows:

I am trying to use data=journal for my root file system. If I add: Kernel /vmlinuz-2.4.7-10 ro root=/dev/hda2 rootflags=data=journal To my grub.conf file, all I get is a kernel Panic, "EXT2-fs: Unrecognized mount option data. Kernel panic: VFS unable to mount root fs on 01:00" My fstab file is: LABEL=/ / ext3 defaults 1 1 Any suggestions?

With Centos3, fedora1/2 I have been able to put /boot on a RAID1 partition and have it boot normally. Unlike earlier versions that used lilo as the default boot loader, these did not make the 2nd drive bootable but at least I was fairly confident that if the first drive failed I could use the install CD in rescue mode to fix up the 2nd one and go on. However, Centos4 won't boot at all with

I am new to ext3 + external journal. Is there any howto I can look at? this is what I understand 1. mke2fs -O journal_dev /dev/md5 2. mke2fs -J device=/dev/md5 /dev/md0 3. mount /dev/md0 / -t ext3 ( hmm.. what do I need to put on fstab?? ) /dev/md5 is a two drive RAID 1 partition /dev/md0 is a 4 drive RAID 5 partition. questions: 1. I am running RedHat 9.0. what extra software I need to

I want to convert the last of my filesystems to ext3. The only one left is /boot. It is not very big however, only about 10MB itself. Any recommendations on what size journal to put a /boot filesystem of only 10-20MB? Oh, BTW: "tunefs -j -J size=..." is awesome. No more gyrations with dd, chattr, lilo -R, etc. Nice! One note however: even in Stephen's 1.20.WIP.sct-20010216

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >

Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's