similar to: kernel panic: Assertion failure in __journal_unfile_buffer()

Hi, I hope this is the right mailing list, I think this is an ext3 error. I was copying a bunch of largish files around last night (between 300MB and 5GB each), and suddenly the partition I was copying to stopped responding - any program accessing files on that partition would lock up, and not even kill -9 would terminate them. I'm not particularly experienced with tracking down

I'm trying to build driver for hpt374 raid controler on a new installation of contOS 4.2 followin the instroctions in this thread http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&order=DESC&topic_id=223&forum=7 It says that I should run "yum install kernel-sourcecode" to get the files I need and it will create the path /usr/src/linux-2.6.9-5.0.3.EL which

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

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:

I've just set up a brand new system with software raid1 (in degraded mode) with one IDE 20GB drive, using kernel 2.2.19pre16 with ext3 0.0.6b. It's split like this.. 32MB /dev/hda1 /boot 2GB /dev/hda2 / ~18GB /dev/hda3 /home all partitions are marked as 0xfd (autostart raid) with the patches from http://people.redhat.com/mingo/raid-patches for 2.2.17. And I've made all the ext3

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

I think I have this one solved, I hope. I think what Andreas and I are running into are a few different assertions. One being the LVM lvm_do_pv_flush caused assertion which is related directly to invalidate_buffers() being called which then triggers refile_buffer() on a journaled buffer, which appears clean in all other ways according to the checks in refile_buffer(). The following is what

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

Hello, I know that this card has support in FreeBSD but I'm curious if anyone has used them under heavy load in a RAID-5 configuration. We're thinking of equipping two of these cards with 8 120GB Hitachi drives and run it in an RAID-5 array for video material. The usual data streams will likely be 2-3 streams at about 5-20MB/s (totally) and I know that a single drive will handle that,

Jun 29 11:30:05 ns kernel: Assertion failure in __journal_file_buffer() at transaction.c:1935: "jh->b_jlist < 9" Jun 29 11:30:05 ns kernel: invalid operand: 0000 Jun 29 11:30:05 ns kernel: CPU: 0 Jun 29 11:30:05 ns kernel: EIP: 0010:[__journal_file_buffer+54/400] Not tainted Jun 29 11:30:05 ns kernel: EFLAGS: 00010282 Jun 29 11:30:05 ns kernel: eax: 00000059 ebx:

I get 2 rejects applying 2.2.19-ext3 to latest errata rh 2.2.19 kernel. 1) fs/buffer.c Should I put "J_ASSERT(buf->b_count > 0);" before or after " *(int *)0 = 0;"? ===== ext3 0.0.7a patch --- 934,946 ---- if (buf->b_count) { buf->b_count--; + if (!buf->b_count && + (buf->b_jlist != BJ_None && buf->b_jlist

SYSTEM: rh6x based system, 2.2.19-6.2.7 rh errata kernel + 0.0.7a patch, I rebuilt rpm for i686; celeron466, 64MB, PIIX4. root fs is on software raid1 ext2, 6 additional fs's on software raid1 ext2. There's a 3rd HD, not mirrored, which is mounted ext3. EXT3-fs: mounted filesystem with ordered data mode. I enabled journal with tune2fs -j with unmounted fs. The 3 HDs are tuned with

Hi all! While I was having some fun, testing different filesystems at home and making some benchmarks, I hit a bug when running Postmark in an ext3 partition mounted with data=journal. I repeated this test twice and got the same results under Linux 2.5, also it was not found while mounting with data=writeback or data=ordered or under Linux 2.4. I don't know if it's a know problem or

Hi, as I mentioned in earlier mail to ext3-users I have been getting some corruption on an ext3 filesystem that has been serving NFS. I am now confident that I fully understand the problem and have a patch. It only affects data=journal mode and I wonder if it might also be the cause of the corruption noted by a number of people on linux-kernel. First I will explain the problem. Then display

Anyone who know if there exist drivers for Highpoints RocketRAID 454 for CentOS? I didn't find any on their site for RedHat Enterprise, which I tought would work with centos, so.. anyone? http://www.highpoint-tech.com/USA/bios_rr454.htm /H?vard

At the risk of angering the crash Gods, my sustem has NOT crashed again since I downgraded the kernel from 2.6.18-1.2239.fc5 to 2.6.18-1.2200.fc5. Given that newfound stability, and my lack of time, I'm going to put on hold any further diagnostics, until the next kernel revision is released. I have submitted a report at bugzilla.redhat.com (bug 218128). (Ah, nuts; accidentally created a

This patch fixes an inefficiency and potential system lockup in the 2.4 kernel's ext3 filesystem. The problem has been present since 2.4.20-pre5. This patch is applicable to 2.4.20. A copy is at http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.20/ext3-scheduling-storm.patch Anyone who is using tasks which have realtime scheduling policy on ext3 systems should apply this change.

Hi, I've recently been playing about with recent ext3 0.0.6b and lvm 0.9.1 beta7 and am now able to trigger an "Attempt to refile free buffer" assertion. This seems to "only" occur when using ext3 on the root filesystem. Possibly that is related to the fact that the lvm utility I'm using to reproduce this problem is modifying data in /etc. The easist reproduction

Hi All, I'm running stable from August 19/2003. I've got a few A7N8X-Deluxe boards. One Rev1.0 and two Rev2.0. While the 1.0 board works, the 2.0 boards lock up on boot during the uhub0 bus discovery. It's extremely frustrating :) ... While I can boot without the devices and attach them later, the devices ( logitech usb keyboard, logitech mouse, rio800, samsung CDMA adapter,

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158