search for: bh_dirty

I previously wrote: > I have come across what appears to be a bug in __invalidate_buffers() > w.r.t. the change in ext3-0.0.6 using BH_JDirty instead of BH_Dirty > for buffers held in the journal. If invalidate_buffers() is called > on a device (LVM likes to do this a lot, for whatever reason), it yanks > JDirty buffers out from underneath the journal layer, and causes an > oops in journal_insert_checkpoint() (line 385, "buffer_dirty(bh) |...

...the problem is. The assert text is as follows: -- cut here -- cut here -- cut here -- cut here -- cut here -- Message from syslogd@dax at Tue Oct 9 12:07:47 2001 ... dax kernel: Assertion failure in jbd_preclean_buffer_check() at jbd-kernel.c:80: "(((bh)->b_state & (1UL << BH_Dirty)) != 0)" -- cut here -- cut here -- cut here -- cut here -- cut here -- Here is line 80 from jbd-kernel.c: -- cut here -- cut here -- cut here -- cut here -- cut here -- J_ASSERT_JH(jh, buffer_dirty(bh)); -- cut here -- cut here -- cut here -- cut here -- cut here --...

...8 test5 kernel: Unexpected dirty buffer encountered at do_get_write_access:618 (03:05 blocknr 3692808) I've duplicated it in 2.4.22 and 2.4.25. Here's the crash from 2.4.25: Assertion failure in journal_commit_transaction() at commit.c:759: "!(((bh)->b_state & (1UL << BH_Dirty)) != 0)" kernel BUG at commit.c:759! invalid operand: 0000 CPU: 0 EIP: 0010:[<c0174064>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010282 eax: 00000074 ebx: f7221f00 ecx: f7752000 edx: f7795f7c esi: f71a9c00 edi: 00000001 ebp: 00000000...

...ine BH_Alloced 11 /* 1 if buffer has been allocated */ + #define BH_Freed 12 /* 1 if buffer has been freed (truncated) */ + #define BH_Revoked 13 /* 1 if buffer has b ===== redhat latest 2.2.19 /* bh state bits */ #define BH_Uptodate 0 /* 1 if the buffer contains valid data */ #define BH_Dirty 1 /* 1 if the buffer is dirty */ #define BH_Lock 2 /* 1 if the buffer is locked */ #define BH_Req 3 /* 0 if the buffer has been invalidated */ #define BH_Protected 6 /* 1 if the buffer is protected */ #define BH_Wait_IO 7 /* 1 if we should throttle on this buffer */ #defin...

...ed dirty buffer encountered at >do_get_write_access:618 (03:05 blocknr 3692808) > >I've duplicated it in 2.4.22 and 2.4.25. Here's the crash from 2.4.25: > >Assertion failure in journal_commit_transaction() at commit.c:759: >"!(((bh)->b_state & (1UL << BH_Dirty)) != 0)" >kernel BUG at commit.c:759! >invalid operand: 0000 >CPU: 0 >EIP: 0010:[<c0174064>] Not tainted >Using defaults from ksymoops -t elf32-i386 -a i386 >EFLAGS: 00010282 >eax: 00000074 ebx: f7221f00 ecx: f7752000 edx: f7795f7c >esi: f71a9c00...

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter

When trying to build ext3 as a module, I get the follwing errors during the kernel link: /usr/bin/kgcc -D__KERNEL__ -I/home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/include -c -o dummy_sym.o dummy_sym.c ld -m elf_i386 -T /home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_t ask.o -Map map

Hi, A system running ext3 crashed this afternoon (nothing to do with ext3, bad network driver). Is was saving a file from emacs when it happened. The file system is 0.06b and had ordered data as the mount option. Let me emphasize this was running ext3 pure, not with SnapFS or InterMezzo layered on top of it. strace reveals that Emacs does open("existing file name", O_TRUNC |