search for: rootflags

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 it's options...

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...

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, Thomas Kupper <thomas@kupper.org> wrote: [...] >> Doesn''t ''cat /proc/mounts'' show the actually used mount options? > >No, it doesn'...

I hate to bother the list with this, but I am lost. With our servers that use LILO we use append=rootflags=data=journal. I have read everything I can find on GRUB, the key is everything I can find, and I have no idea how perform the same function in grub.conf Randy

...g 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 option. For example: LILO: linux rootflags=data=journal ------------------------ Thanks, --jeff

Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa

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: LABEL=/ / ext3 defaults 1 1 LABEL...

...ting. If it's any use, here is my modest QEMU command line > collection. > > $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ > -m 1024 \ > -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ > -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init rootfstype=9p > rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' \ > -serial stdio \ > -fsdev local,id=root,path=$dir,security_model=none \ > -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root \ > -monitor none This is similar to what virtme does, except that virtme will give you a much m...

...ting. If it's any use, here is my modest QEMU command line > collection. > > $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ > -m 1024 \ > -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ > -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init rootfstype=9p > rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' \ > -serial stdio \ > -fsdev local,id=root,path=$dir,security_model=none \ > -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root \ > -monitor none This is similar to what virtme does, except that virtme will give you a much m...

...010-01-12 11:54:13.000000000 +0100 +++ cobbler-import 2010-02-08 10:31:44.000000000 +0100 @@ -46,15 +46,9 @@ cobbler distro add --name="oVirt-Node-$node_arch" --arch=$node_arch \ --initrd=$node_dir/tftpboot/initrd0.img -- kernel=$node_dir/tftpboot/vmlinuz0 \ - --kopts="rootflags=loop root=/ovirt-node-image.iso rootfstype=iso9660 ro console=tty0 console=ttyS0,115200n8" + --kopts="rootflags=loop root=live:/ovirt-node-image.iso rootfstype=iso9660 ro console=tty0 console=ttyS0,115200n8" I didn't try this patch but I think this is the way to get this k...

...gt; > >> -m 256M \ > > >> -machine pc-i440fx-2.1,accel=kvm \ > > >> -netdev tap,id=net0 -device > > >> virtio-net,netdev=net0,mac=52:54:00:12:36:34 \ > > >> -smp 1,sockets=1,cores=1 \ > > >> -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro > > >> rootfstype=9p console=ttyS0' > > >> > > >> And here my libvirt VM config: > > >> <domain type='kvm'> > > >> <name>irc</name> > > >> <uuid>ffbd32eb-...

Hi all, I was trying to mount root-partition which is ext3 partition with noatime and ro option. I included "ro" in the kernel command line But for mounting it with "noatime" option when I searched for some solution I came across a patch http://lkml.org/lkml/2007/8/5/38 But after applying this patch and including option "noatime" in

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.

Hi, http://www.syslinux.org/wiki/index.php?title=Config > DEFAULT > > DEFAULT command > > Set the default command line (which often references a LABEL). I have tried default vmlinuz-4.12.13_1 root=.... rootflags=.... initrd=.... but vmlinuz does not get executed. I was given a prompt ("boot:"). Despite that "prompt 0" and "timeout 0" are present in the cfg. With using a label and, after the label, "linux" + the above command line, vmlinux does get executed fine. S...

...io-9p-pci,fsdev=r,mount_tag=root \ >> -nographic \ >> -m 256M \ >> -machine pc-i440fx-2.1,accel=kvm \ >> -netdev tap,id=net0 -device >> virtio-net,netdev=net0,mac=52:54:00:12:36:34 \ >> -smp 1,sockets=1,cores=1 \ >> -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro >> rootfstype=9p console=ttyS0' >> >> And here my libvirt VM config: >> <domain type='kvm'> >> <name>irc</name> >> <uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid> >> <memo...

...al,id=r,path=/srv/overlay/run/irc,security_model=passthrough -device virtio-9p-pci,fsdev=r,mount_tag=root -nographic -m 256M -machine pc-i440fx-2.1,accel=kvm -netdev tap,id=net0 -device virtio-net,netdev=net0,mac=52:54:00:12:36:34 -smp 1,sockets=1,cores=1 -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro rootfstype=9p console=ttyS0' And here my libvirt VM config: <domain type='kvm'> <name>irc</name> <uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid> <memory unit='KiB'>262144</memory> <currentMemory...

...oot 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 data=ordered. I see where one procedure is to use lilo -R linux rw rootflags=journal=update. I'm confused about the read&write aspect as well as why they used journal=update instead of data=journal. This filesystem was created new with this system, so I should not have to upgrade it. Thanks.

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 check in rc.S? Or what? Thanks. Folkert van Heusden [ www.vanheusden.com ]

not just console= This is to allow vendor-specific boot parameters to survive when the image is installed to disk. Signed-off-by: Alan Pevec <apevec at redhat.com> --- scripts/ovirt-early | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/ovirt-early b/scripts/ovirt-early index 4b85102..c17ea74 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@

Well, I had the first use of the recovery mode on the RH 8.0 install CD today on a dev system. I changed the mount option for the root partition to data=writeback to see what all the claimed speed increases are about, and the system failed to mount the partition r/w, so the resulting boot failed. After search usenet, it seems other RH folks have had this problem, possibly because it is