similar to: Am I using journalled data mode?

I am using the srpm from http://xenbits.xensource.com/kernels/rhel3x/kernel-2.4.21-47.0.1.EL.xs0.3.5. 15.src.rpm (I get the same issue using the binary RPM) the dom0 is running 3.0.3_0 Upon booting the DomU, (the DomU has been passed phy:/dev/sda6, which has been partitioned using qemu) I get the following ioctl errors. ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported

excuse the newbie nature of the post, we recently inherited a linux server which has ext3 on it and we have encountered problems before being afforded the opportunity to properly educate ourselves... We had a situation where the server froze and required a hard restart. On reboot we get the following notices which were captured in the dmesg log EXT3-fs: INFO: recovery required on readonly

A scsi error (caused possibly by a loose cable) has left the processes accessing my ext3 file system hung in an unkillable state after it triggered an assert in ext3's journaling layer. I assume my only recourse at this point is to reboot. Please correct me if I'm wrong. Log messages appended. Thanks, -Jim Nov 21 04:04:04 attila kernel: SCSI disk error : host 0 channel 0 id 5 lun 0

Do you know what can cause the smbd process to steal out the cpu usage (99%) and keep running like that for days? I have a Samba PDC 3.0.1pre3 running on top of RH9 2.4.20 kernel. Below is the current top report. Strangely, the PDC still responds in reasonable good response times to heavy network duty.traced the log.%machine name% and didn't find anything . I haven't tried to restart smb

While investigating erratic performance on one our our servers, I'm getting some very odd performance stats coming from vmstat. What initially appeared to be happening is the machine goes into a hard loop in some mod_perl webserver code. Now there still may be an issue with the code, but my code examinations show no possible way this could be happening, but what I'm writing to you

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)

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

Hello! While performing some zttest's for some time today, I was also keeping an eye of a top of the machine. While the zttest was running, I also had a ssh-keygen and a dd creating a 5GB file on an EXT3 partition running. I noticed that for the most part, I got a decent number of 100%'s, and a bunch of 99.6%'s or higher. However, it seems that whenever the zttest dropped

Hi, A couple of our important servers, both running FC4 but one i386 and one x86_64, have been crashing recently. They both are running ext3 data=journal with large external journals and high commit intervals. Both machines use the gdth driver for their hardware RAID sets, if that's of any use. I think the hardware is good in both cases. I hope someone finds this data useful enough to be

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

It appears that this bug in data=journal mode, https://listman.redhat.com/archives/ext3-users/2005-February/msg00045.html isn't fixed in 2.6.11.11. Andrew, I've CC'd you since you have previously looked at this specific issue. I'm seeing this problem on dual-Opteron x86-64 boxes serving NFS + Samba3 to a few dozen clients; it takes several hours at high load to reproduce. We

Hello All, I am running Linux 2.4.7-10, 2.4.18-4 and 2.4.19-pre9, I see the following oops quite often (mainly on 2.4.19-pre9 with kdb). All the kernels I use have the kdb patch installed. 1 kmem_cache_alloc (offset 0x125) get_unused_buffer_head journal_write_metadata_buffer journal_commit_transaction kjournald kernel_thread kmem_cache_alloc dis xchg %eax, (%ebx) cmp $0x5a2cf071, %eax (where

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

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

I've been running into a kernel panic pretty consistently when using data=journal. This occurs during heavy IO, and is highly reproducible (only takes about 5 minutes of IO to cause it). The applications being used are MySQL, Postfix, and a mail filtering application which operates on postfix queue files using mmaped IO. Shortly before the crash, the following messages are logged: Mar

Greetings all, I am curious if anyone knows why utilities such as 'GNU shred' (part of coreutils) and 'wipe' say they are not effective on journalled file systems- especially EXT3. Is it because you can't "guarantee" that the journal has been flushed/wiped (i.e. you have the journal 'between' you and the actual data blocks on the physical disk), or because

Hello everyone. I'm running Red Hat 7.3 with kernel 2.4.18-10 and all errata patches installed. My system has been running for over three years without any problems. All I've done to it in that time is add a mirror set of two 80GB drives, a Promise IDE controller, and upgrade Red Hat through the 7.x series. Right now I have three drives. A 13GB system drive off the motherboard, and

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?

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