similar to: "DRQ after issuing write" error

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

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

Hi all, One of our mx servers started misbehaving today (postfix would timeout internally, load rising) and after I tried to reboot it, I got this: Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:613: "transaction->t_forget == NULL" ------------[ cut here ]------------ kernel BUG at fs/jbd/checkpoint.c:613! invalid operand: 0000 [#1] PREEMPT SMP Modules

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

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

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

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

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

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

Hi. I have a RHEL server that has some errors in dmesg , what do they mean, how do I fix them ? mtrr: type mismatch for f9000000,800000 old: write-back new: write-combining mtrr: type mismatch for f9000000,1000000 old: write-back new: write-combining mtrr: type mismatch for f9fe0000,10000 old: write-back new: write-combining mtrr: type mismatch for f9fc0000,20000 old: write-back new:

Unable to handle kernel NULL pointer dereference at virtual address 00000004 printing eip: 42839407 *pde = 00003001 Oops: 0002 [#1] SMP Modules linked in: md5 ipv6 autofs4 e100 mii ipt_REJECT iptable_filter ip_tables floppy sg scsi_mod microcode dm_mod ohci_hcd ext3 jbd raid1 raid0 CPU: 1 EIP: 0060:[<42839407>] Not tainted EFLAGS: 00010202 (2.6.8-1.521smp) EIP is at

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

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

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 >

Ext3 Journal oops & RAID-1 set losing sync. (Sent to both EXT3 and Linux-RAID since both are in use and seem possibly relevant) I have had a number of problems maintaining a software RAID-1 set on an IDE box I maintain; it seems that doing raidhotadd on the drive marked as invalid works each time though. However, I've had both errors about trying to read past the end of the

I upgraded my Centos 4.7 server last night. Switched from a cheaper 50$ asus motherboard to a Supermicro motherboard. I also, using dd, copied entire 500g SATA seagate drive to new 500g SATA seagate drive so as to have two copies in case something went wrong. Anyway, now I keep getting this error: Nov 21 06:08:33 server kernel: hda: status timeout: status=0xd0 { Busy } Nov 21 06:08:33 server

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Background: Large NFS/mail server. Dual PIII/1GHZ. 4GB memory. Mylex AcceleRAID 352 RAID controller (uses DAC960 driver). Intel eepro100 network cards. RedHat 7.3 with all errata. Kernel-2.4.18-5smp. 2GB of memory is used by a RAM disk for mail queue. ext3 filesystems (switched to ext2 to see if that helps). one large (100GB data partition).

I have 3 OQOs with Centos and I frequently get the following error messages: Jan 28 13:18:07 oqo3 kernel: hdc: status timeout: status=0xd0 { Busy } Jan 28 13:18:07 oqo3 kernel: ide: failed opcode was: unknown Jan 28 13:18:07 oqo3 kernel: hdc: no DRQ after issuing MULTWRITE Jan 28 13:18:07 oqo3 kernel: ide1: reset: success I have Fedora 10 on a fourth unit and it NEVER gets this message. I

Hi, I am getting the following Oops on 2.6.30.1 kernel. The bad part is, it happens rarely (twice in last 1.5 months) and the system is pretty lightly loaded when this happens (no heavy file/disk io). Any insights or patches that I can try? (i searched lkml and ext3 lists but could not find any similar oops/reports). == Oops =================== BUG: unable to handle kernel NULL pointer