similar to: Re: Ext3 initrd

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

I referred to the entry rootfs / rootfs rw 0 0 in the output of "cat /proc/mounts", that is not really very much explicative, due to the setting "auto" in /etc/fstab and to the fact that file system had has_journal flag and no ext3 module was mounted. But I was wrong: I think that if you have an ext3 fs and you mount it as ext2, you continue to see the has_journal flag with

Hi there, I tried to setup my linux box with an ext3 root file system. That failed because of wrong initrd settings. Sorry. Now the filesystem is marked having a journal but there is no /.journal file anyway. I tried to buikd that journal by hand (tune2fs -j /dev/hda3 - in my case). That fails also. :-( /sbin/tune2fs -l /dev/hda3 says: ... Journal UUID: <none> Journal

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

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

Hello ext3-users-request, request ======= 2004-03-03 12:00:00 You writed======= >Send Ext3-users mailing list submissions to > ext3-users at redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/ext3-users >or, via email, send a message with subject or body 'help' to > ext3-users-request at redhat.com >

Hello, I recently switched from 2.2 to 2.4 kernel. Each partition already contains a journal. I tried kernel-2.4.5-0.2.9 from RedHat Rawhide, where ext3/jbd is modularized. For the people who want to try this kernel, you first need to rebuild it, and enable CONFIG_JBD_DEBUG. This solves an unresolved symbol in jbd.o which prevents ext3 to load. (This issue will be solved in next RawHide) My

On 28 Feb 2002, Stephen C. Tweedie (sct@redhat.com) wrote: > Hi, > > On Sat, Feb 23, 2002 at 02:55:33PM +0100, Jan Söderholm wrote: > > > I use RH 7.2 (the download version) with kernel 2.4.9-13 (upgraded by > > using the Up2date program). Today i used Up2date (version 2.7.11) to > > upgrade to 2.4.9-21 (kernel, headers and source). I get the following >

Hi, after my X froze i had a fs inconsistency after the journal replay [...] EXT3-fs: 03:06: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 64k freed INIT: version 2.78 booting Loading /etc/console-tools/default.kmap.gz Activating swap... Adding Swap: 264560k

Hello, I'm using RedHat 7.2. I needed to mount my root fs to QNX 6.1. QNX supports ext2 only but I tried that anyway. It was mounted wrong (e.g. the /root directory was symbolic link to non-existing file). When I wanted to boot from the RedHat again, these errors occured: ... Mounting root filesystem EXT3: failed to open journal device unknown-block(0,0):-19 mount: error 22 mounting ext3

Hi, I am running RH 9.0 with Grub. I just added an additional "old" drive from another system which has Win98 (fat32) and RH 7.2 (ext2) installed. However, now when I boot up, I am getting the following errors: ext3: No journal on filesystem ide3(34,7) mount: error 22 mounting ext3 pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 umount /initrd/proc failed: 2 Freeing unused

Hi all, and particularly Andrew and Stephen, I recently "upgraded' one of my NFS fileservers from (patched)2.4.18 to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure problem). Unfortunately I have experienced what appears to be a deadlock. The one I will describe was experienced while running 2.4.23-pre7, though I had a very similar problem in 2.4.22 (but

Hi, I am a new ext3 user and I am having problems similar to what many people are facing on this list. I have done everything as the emails suggest. I am using SuSE 7.3 with the the 2.4.10 kernel and ext3 compiled as a module. Because it is 2.4.10 kernel, I created all my journals from a rescue disk and everything seems to be working right for the non-root filesystems. My fstab has all my

Hello, I'm using RedHat 7.2. I needed to mount my root fs to QNX 6.1. QNX only support ext2 but I tried that anyway. The disk was mounted bad (for example the /root directory seemed to be symbolic link to a non-existing file). When I wanted to boot from the RedHat again, these error messages occured: ... Mounting root filesystem EXT3: failed to open journal device unknown-block(0,0):-19

When I first installed ext3, it worked as expected. After a crash, journals would be played, and no fsck. Now, every crash causes an fsck, just like it were a regular ext2, even though / has a journal and is being mounted as ext3. Some fs info for / Filesystem features: has_journal filetype sparse_super Filesystem state: not clean Errors behavior: Continue Some fs info for

First of all you must be able to boot. Thus you must press 'e' when your grub screen appear with selection highlights on Red Hat Linux. Highlight line consisting 'initrd...' and press 'd'. Press 'b' to boot. Because your partition does not have a journal on it, create one with these steps below. - Make sure you remember the device attached to ide3(34,7), it is

Greetings, I recently cpio-ed some user directories onto a new ext3 partion. After putting this file server's partition into production, I noticed a .journal file in the root directory of the partition dated well before the creation of this partition. I think this .journal file was copied over from the old filesystem and I am concerned that I over-wrote this current filesystem's

Hi, I am trying to compile the kernel with ext3 support and i downloaded the 2.4.13 kernel and patched it for RH 7.2 to update from the 2.4.7 precompiled ext3fs kernel. Then i selected ext3 support and and the JBD debugging support under 'make xconfig.' Then i ran the following commands make clean make dep make bzImage make modules make modules_install cp arch/i386/boot/bzImage

Hi all, Im network booting initrd-2.6.9-22.EL.img from pxelinux. <snip from init script> echo Creating root device mkrootdev /dev/root umount /sys echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot mount -t tmpfs --bind /dev /sysroot/dev echo Switching to new root switchroot /sysroot echo UMOUNTING initrd-dev umount /initrd/dev </snip> I receive error

Hi. While reading Documentation/filesystems/ext2.txt I noticed that the information about ext3 is outdated: The ext3 code is currently (Apr 2001) available for 2.2 kernels only, and not yet available for 2.4 kernels. Journaling (ext3) ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/ The file was touched when I applied the 2.4.7 patch from Linus, so I suspect it's maintained. --