similar to: Changing root journal data mode

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

On my Debian box: Package: lilo Version: 1:22.2-5 Severity: normal lilo seems to cause a kernel warning (see subject) when / is a ext3 partition. Maybe a kernel problem? Who knows. I'm running 2.4.19-rc1-ac7 -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux hummus 2.4.19-rc1-ac7 #1 Wed Jul 17 22:14:20 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions

Hi, I've been wondering exactly what you gain by using journaled mode over ordered mode. Are there any known cases where journaled mode could recover where ordered mode wouldn't? Mike

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:

Hi, again I ran into some difficulties while setting up my / - partition under v0.0.5. With the conversion of my /home - partition went everything well. Even under heavy load I didn't remark anything unusal - apart from a little performance-issue. My current setup is now the following: / - partition: no conversion possible: V1-journal with journal-data mode /home - partition: conversion

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

Hello, I have this bug report that I have filed. Is there any specific reason why samba behaves this way, and doesn't use the unix semantics? Since this is even more restrictive than unix semantics, I'm more inclined to call it a bug until I know it's supposed to be this way. Any ideas? ----- Forwarded message from Mike Fedyk <mfedyk@matchmail.com> ----- From: Mike Fedyk

Greetings all, I have hit a kernel BUG in revoke.c in kernel 2.4.7-ac7 twice today while attempting to perform the same operation (patching stock 2.4.8 kernel src with "patch -p1 < patch-2.4.8-ac4"). Syslog entries follow. Please email me if you want/need my kernel config or any other information. Thanks, jtp

quotacheck takes longer than fsck on our ext2 fileservers. Is this redundant in ext3? Do I need data=journal? Cheers, Matt

Hi, After mounting -t ext2 an ext3 partition, working with, do I have to recreate .journal when I remount the partition as ext3 ? Thanks ! Liu

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I created all my ext3 partitions a while back, so the journal.dat file is visable. I'd like to remove them and use the new tune2fs functionality. Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and then remount as ext3? Or am I missing something? thanks! - -- Douglas J. Hunley (Linux User #174778)

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

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

Hi, I've downloaded and installed kernel-2.4.9 from rawhide in order to use ext3 support (I've also upgraded the necessary packages). I've used tune2fs to make the current ext2 partitions (incluind /) and changed fstab to reflect that. In order to test if everything is ok (this is a test machine) I've switched off with no shutdown. Except the / all other partitions accused

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,

Hello. On a server running 2.4.25, I have the two following errors in the kernel logfile: Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Should I worry about them (disk failure, filesystem damage) ? Thanks. As an addition what does the pair '08:11' means ? Is

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

Something bad must have happened when I first ran e2fstune on my root file system. Now I cannot mount it ext3 and when I try to run tune2fs -j on it, I get this error message: permission denied while trying to create journal file There is a .journal file in /: [root@monster log]# ls -l /.journal -rw------- 1 root root 33554432 Sep 29 10:21 /.journal But dumpe2fs

Hi, While doing some stress testing with presto module from the intermezzo project layered over ext3, I got the following assertion failure: Jan 17 23:09:55 planck kernel: Assertion failure in jfs_prelock_buffer_check() at journal.c line 410: "bh->b_jlist == 0 || bh->b_jlist == BJ_LogCtl || bh->b_jlist == BJ_IO || bh->b_jlist == BJ_Data" Jan 17 23:09:55 planck kernel: