search for: bh_uptodate

Hi, By running some scripts on our target system for a while, I lost all means of access to the system. It seems that the kernel is crashed with the following error message: Assertion failure in do_get_write_access() at transaction.c:731: "(((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0)" Oops: Exception in kernel mode, sig: 4 We are currently running Linux version 2.4.18. I assume that the problem has been fixed. Can anyone tell me which version of linux kernel has the fix or where can I get the fix? Thanks a lot in advance. Regards, Joe Zhao -------------- next p...

We have DELL 2650 with CENTOS 3.4 installed. Today I saw following messages on /var/log/messages. Anyone know what it mean? Does it point to which disk? =================================== Jun 4 06:58:40 ORA03 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Jun 4 06:58:40 ORA03 kernel: Possible IO failure. Jun 4 06:58:40 ORA03 kernel: Jun 4 06:58:45 ORA03 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Jun 4 06:58:45 ORA03 kernel: Possible IO failure. Jun 4 06:58:45 ORA03 kernel: Jun...

...t;>] ocfs_check_volume [<>] ocfs_mount_volume ...... ------------------------------------------------------- I think I found the root cause of the bug reported in mark_buffer_dirty(). It is caused in the Linux journaling routine(JBD) journal_create(). In kernel 2.6.x, buffer_head state BH_Uptodate is checked in mark_buffer_dirty(), while kernel 2.4.x doesn't do. If this state doesn't exist in the buffer_head, buffer error information is reported. But, in routine journal_create(), the state BH_Uptodate is set after the call to mark_buffer_dirty(). This works well in kernel 2.4.x, bu...

...ckFree 10 /* 1 if alloced and freed quickly (see below)*/ + #define 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_W...

Hi - We have had a raid failure, we have some what recovered but we continue to see the following ext3 message... Apr 17 14:59:14 acnlin84 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Apr 17 14:59:14 acnlin84 kernel: Possible IO failure. Since we have experienced several instances of ext3 file system corruption when we lose total communication with our raid, we were wondering if there was any concrete advice out there on what to do in this situation. Othe...

I got this.. The system was usuable, but not very. If I tried to access the ext3 volume, it would hang. Reboot hung too, complaining about too many open files. Any ideas? I have no idea what triggered it; this is a big file/web/mail server, with all of that on the ext3 volume. And I've never run ksymoops before, but I think I did it right. - Josh Assertion failure in