similar to: Ext3-users digest, Vol 1 #1063 - 1 msg

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

Hi Ext3! I'm running about 30 dedicated MySQL machines under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had

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

All, I know that there is no official port to Kernel 2.4.4, thus I may not get any help, however I am hoping someone could point me in the right direction for my problem. I am currently forced to use kernel 2.4.4 for reasons out of my control (embedded board). Here are the exact versions of everything I'm running: ExT3 Version: ext3-2.4-0.9.6-248 Util Version: util-linux-2.11f.tar.bz2 e2fs

Hello, I am not subscribed to this mailing list. My apologies if non-members are not allowed to post in this forum. I have a Linux-2.4.19pre10aa4 computer and I have seen an error message "Unexpected dirty buffer encountered at do_get_write_access:598 (03:05 blocknr 0)" appears in the log. With a little bit of research I found that this message is printed from fs/jbd/journal.c,

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

While writing a file to an ext3 filesystem, i get some drive errors on the console. I guess is a drive/ide related problem more that a ext3 one, but anyway the debug output is here if you want to take a look. And, by the way, what means that DRQ thing?? Oct 7 20:31:36 fargo kernel: (journal.c, 218): kjournald: kjournald wakes Oct 7 20:31:36 fargo kernel: (journal.c, 202): kjournald:

I use redhat7.3 . Sep 20 20:39:31 Xhwsrhtrs2 kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" Sep 20 20:39:31 Xhwsrhtrs2 kernel: ------------[ cut here ]------------ Sep 20 20:39:31 Xhwsrhtrs2 kernel: kernel BUG at commit.c:535! Sep 20 20:39:31 Xhwsrhtrs2 kernel: invalid operand: 0000 Sep 20 20:39:31 Xhwsrhtrs2 kernel: autofs eepro100

It's both in 2.6 and recent 2.6 (for RH ASS2.1 you'll probably need to copy the latest 2.4 defintion, but I don't care for obsolete junk). Index: src/super.c =================================================================== --- src/super.c (revision 1014) +++ src/super.c (working copy) @@ -799,7 +799,7 @@ /* get first two blocks */ for (i=0; i<2; i++) { - bhs[i] = getblk

Hello,ext3-users: Yep, We meet the same problem. Jul 17 22:41:40 sh_intel5 kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" Jul 17 22:41:40 sh_intel5 kernel: ------------[ cut here ]------------ Jul 17 22:41:40 sh_intel5 kernel: kernel BUG at commit.c:535! Jul 17 22:41:40 sh_intel5 kernel: invalid operand: 0000 Jul 17 22:41:40 sh_intel5

Hello: My RedHat 7.3 machine just locked up and I could not reboot it. I had to punch the reset button. Here is what I found in the /var/log/messages file: May 19 12:50:16 server1 kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" May 19 12:50:16 server1 kernel: ------------[ cut here ]------------ May 19 12:50:16 server1 kernel: kernel BUG

We're getting the below errors about once a day on a system we're trying to set up with RedHat 7.3. This has happened to multiple filesystems on multiple physical and logical disks (basically we've got 4 drives as 2 sets of RAID 1 arrays, details below). Until a week ago, this box was a high-volume IMAP server running RedHat 6.2 with uptimes in the 200-day range, so I don't

I don't know enough about it to know whether this is a known problem (I couldn't make much sense of what I found on Google), but it seems to be a journal-related issue. Is it likely that data has been corrupted? Do I need to take any action? 2.6.12-9-amd64-k8-smp, Ubuntu 5.10, dual opteron 2GB Jan 23 03:08:22 infinity kernel: [24686.841032] Unable to handle kernel NULL pointer

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

Anyone got a clue about this: Server: DELL EdgeServer 2550 with PERC RAID card RH 7.3. Interestingly it happen with PureFTP and then started to hang socket connections until the box hung.. (or was it something else - maybe I have it backwards... that's why I'm comming to you guys..) Log entry in /var/log/messages: Jul 16 01:45:34 ETG3 kernel: <0>Assertion failure in

This patch contains the following cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL: - journal.c: journal_recover Signed-off-by: Adrian Bunk

Today our mailserver froze after just one day of uptime. I was able to capture the Oops on the screen using my digital camera: http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/ Keywords: EIP is at journal_commit_transaction, process kjournald # mount /dev/cciss/c0d0p6 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts

Hi all. I am running the 2.4.18-3smp kernel and over the poast couple of days, ext3 has been crashing. Here is the output: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" ------------[ cut here ]------------ kernel BUG at commit.c:535! invalid operand: 0000 loop autofs nfs lockd sunrpc 3c59x ns83820 ide-scsi ide-cd cdrom usb-uhci usbc CPU: 0

Started with buffer.c v1.19. Reversing change works for me in linux-2.4.6. Loaded 16705 symbols from /lib/modules/2.4.6-pre3/System.map. Symbols match kernel version 2.4.6. Loaded 256 symbols from 12 modules. Linux version 2.4.6-pre3 (root@home1) (gcc version 2.95.3 20010315 (release)) #2 Wed Jun 13 19:53:28 EDT 2001 ----- SNIP ------- VFS: Disk change detected on device ide1(22,64) Assertion

Hello! I got oops after about 3 hours of uptime. Load was about 1,5. This is output of ksymoops after forced reboot if it helps someone. :-) ksymoops 2.4.0 on i686 2.4.14-pre8. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.14-pre8/ (default) -m /boot/System.map-2.4.14-pre8 (default) Warning (compare_maps): mismatch on