similar to: ext3 related oops in 2.4.{18,20} on sparc

Hello, We have about 20 - 30 embedded machines running Linux 2.4.13, which the ext3-2.4-0.9.13-2413 patch applied. These are PowerPC 7410 based systems. I am getting reports of Oops happening either during removes (rm's), or coppies (cp's). Most reports state that issuing the same command once the system boots back up, does not cause it to crash. I guess its something else leading up

We have here an knfs fileserver running ext3 on 2.4.18 kernel with three filesystems: <CLIP> Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda3 10080520 3609632 6368476 37% / /dev/hda4 16437332 12295408 3974932 76% /home /dev/md1 1024872060 409906136 614441636 41% /fs </CLIP> The /fs filesystem lives on a

Okay, after playing around a bit more, I'm getting two oopes in a row when running dbench 16 or dbench 32. Decoded, here they are: Assertion failure in unmap_underlying_metadata() at buffer.c:1530: "!buffer_jlist_eq(old_bh, 3)" kernel BUG at buffer.c:1530! Oops: Exception in kernel mode, sig: 4 NIP: C003BB34 XER: 00000000 LR: C003BB34 SP: CF881E00 REGS: cf881d50 TRAP: 0700 Using

One of our servers (false) just oopsed. In the middle of lunch. Any advise? On console: false kernel: Assertion failure in journal_start() at transaction.c line 245: "handle->h_transaction->t_journal == journal" In kernel log (ran it through ksymoops): Nov 13 12:35:37 false kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Nov 13 12:35:37

Hi, just had an oops while spool uucp mails via uuxqt->postfix->procmail to multiple mailboxes on an UDMA IDE drive on my Laptop. All filesystems are ext3 and i am running 2.2.19 + ext3 + ide udma patches. When rebooting the system hang - After another reboot everything went smooth. invalid operand: 0000 CPU: 0 EIP: 0010:[<c014ca15>] Using defaults from ksymoops -t elf32-i386

Hi [1.] One line summary of the problem: rsync segfaulting and the kernel oops'ing while synchronizing two smbfs's [2.] Full description of the problem/report: I am implementing file synchronization between two Windows NT 4 machines through two smbfs mounts. Rsync runs for about half an hour; then the kernel gives an oops and rsync segfaults. Hereafter the smbfs file system is

Just to make sure somebody reacts (please) I'm forwarding this. Please cc me on replies as I'm not subscribed to this list. -------- Original Message -------- Subject: [RESEND] 2.4.20: ext3: Assertion failure in journal_forget()/Oops on another system Date: Wed, 04 Dec 2002 21:27:31 +0100 From: Andreas Steinmetz <ast@domdv.de> To: Linux Kernel Mailing List

Hi, i am seeing an oops (every couple of days) on a UP PII system with SCSI disks, Kernel 2.2.19 and ext3 0.0.6b. All oops output passed the klogd thus i cant anymore pipe it through ksymoops - I ensured klogd got the correct System.map so the result should be reliable. Apr 25 17:03:10 Unable to handle kernel paging request at virtual address 8efd1fc8 current->tss.cr3 = 0981e000, %%cr3 =

Ah, Mondays. The following oops happened after approximately eleven days of uptime. The machine was not under any particular load at the time. Following a forced reboot, all filesystems replayed the journal successfully. Relevant log entries leading up to the oops: Nov 4 04:54:08 localhost kernel: attempt to access beyond end of device Nov 4 04:54:08 localhost kernel: 03:02: rw=1,

Hi, oops in iput - Kernel 2.2.19/i386 + ide-udma patches + ext3 patches (0.0.7a) Intel BX chipset, SCSI Disks Symbios chipset - The crashing process is the master process of "postfix" an MTA. Just before the crash all processes on that machine started to segfault in nameserver resolution (remote dns server) and after 2-3 minutes this oops happened. ksymoops 2.3.4 on i686 2.2.19.

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

Back again with another oops, which looks suspiciously similiar to the one i posted some days ago (https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html). Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" ksymoops 0.7c on i686 2.4.18-4custom. Options used -V (default) -k

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the

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, I got the OOPS below on my laptop running vanilla 2.4.20-ac2; I had to copy it byhand so it may not be 100% accurate. It hasn't happened again, and this is the first problem I've had with this kernel (or any other kernel, for that matter.) Anyway, I'm not sure, if a) this is actually an ext3 problem, b) OOPS reports of 2.4.20-ac2 are of any interest, so I won't bother with

Anyone try this yet? ftp://ftp.valinux.com/pub/software/kernel/beta/2.4.5-beta2va3.11/ List of SRPM contents follows. -- TheBS atomic-lookup.patch atomicalloc.patch byteprofiling.patch comtrol-1.23.patch configs-2.4.5.tar.gz copy-user-reschedule.patch dac960-enclosure-quiet.patch dma-livelock-fix.patch e100-1.5.5.tar.gz e1000-3.0.7.tar.gz eepro100-speedo-1.patch emu10k1-tone.patch

Hi, Doing the following I can generate an assertion in ext3 0.0.7a. I have an ext3 filesystem on /foo. I export /foo via nfs. I then mount via localhost:/foo onto /mnt. Start up a dd to generate a file on the nfs mount. (cd /mnt; dd if=/dev/zero of=./dd.out bs=1024k), then on the localhost filesystem /foo I rm the file. rm -f /foo/dd.out. This results in "ext3_free_inode: bit already

Oh gurus of ext3... We have an application (it's essentially a watchdog) that monitors i/o on the root partition of our Linux system. What we would like to have happen is in the event that the root file system "goes away" (e.g. the SCSI cable is pulled from the storage device containing the root drive), we want to panic the kernel. We have tried using the "-e panic"

I sent this report sometime ago to l-k and to the preempt-patch maintainer, but omitted to send a copy here, where some people could have clues about the problem - so here it is: ----- Forwarded message ----- To: linux-kernel@vger.kernel.org, Robert Love <rml@tech9.net> Subject: oops with 2.4.18 and preempt patch, on SMP + ext3 machine Coming back home tonight, I found my machine in a bad

HI list! We regularly experience kernel Ooops on our alpha SX164 with ext3 on md on ide controller: No modules loaded, lsmod empty, self compiled kernel ksymoops 2.4.5 on alpha 2.4.25. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.25/ (default) -m /boot/System.map-2.4.25 (default) Warning: You did not tell me where