similar to: ext3 mode

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

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. I just installed ext3 for 2.4.5 from http://www.uow.edu.au/~andrewm/linux/ext3/ but couldn't find anything about converting my root partition to ext3. 2 partitions are now ext3 after I umount and tune2fs, but what should I do with / ? I tried init 1 and umount, but tune2fs would fail because it was on read-only fs. Another question is if I can now build ext2 as a module, and if it's

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

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

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

I have a Debian system from a Knoppix distribution. I started out with ext2 but decided to change to ext3. tune2fs -j OK. However the system boots with a warning ....ext3 mounted as ext2. proc/mounts confirms this and no journal is running. So I have to make an initrd. Did so using instructions in the Debian Reference and this did not change anything. Any attempt to use the img produced was a

Hi all, I am testing new kernel on a mips machine (64 bits for kernel, 32 bits userland) and I found a problem when mounting the root file system. It is an ext3 file system that is correctly mounted as read only. While booting the system remount the file system as read/write and keep starting all daemons. Moving from 2.6.26 to 2.6.30 kernel, I get this error while remounting the file system

Hi, I just converted all my hard disk filesystems from ext2 to ext3. This worked perfectly fine for all non-root fs, but I am having trouble converting the root fs, too. Here's what I did: 1. rebuilt my kernel (2.4.20, x86) with ext3 support linked in statically - no module. 2. Added a journal file to my root fs using 'tune2fs -j'. 3. Added 'rootfstype=ext3' to the

Dear list readers - it was brought to my attention that during the upgrade of a server to rh7.2, and selecting the ext3 migration works well with 1 exception that i need verified if i could please. i heard that once you migrate to ext3, you may no longer do a kernel upgrade without downgrading to ext2 and then putting the kernel or AC kernel in place 'patched'. What i need to know

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

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

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 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 guys'n'girls, I think my question is : How can I tell a redhat 2.4.x kernel (via grub or LILO command-line parameters) that the root filesystem is ext2 and not ext3 ? I thought it would just look in /etc/fstab, but presumably it needs to know what fstype the root is before mounting it; the words 'chicken' and egg' spring to mind. Or does some initrd jggerypokery go on?

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

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

I thought I understood things, but I guess not. I recently configured a new system for a colleague as follows: 1. Redhat 7.1 install Dell Inspiron 8100 - three partitions on 30G - /, /boot, swap 2. Boot up 3. configure, make, make install of linux-2.4.12-ac3 (with approriate lilo changes) lilo (but no reboot until 8) 4. rpm -U mount-2.11g-5.i386.rpm (from rawhide)

I am using SuSE 7.3 compiled ext3 support into the kernel and installed it. All my partitions load up as ext3 except / . I ran tune2fs several times, still doesn't take on the / drive. Most recent dumpe2fs -h show no features on that drive=, I keep going around in circles, removing .journal from / and running tune2fs but it never works for / What am I doing wrong? ( thanks in advance)