Re: Ext3 and/or SCSI bug?

[Andrew Morton]

Gertjan van Wingerde <gwingerde@xxxxxxx> wrote:
>
> Below is an part of my dmesg output that I captured when all of a sudden one
> of my filesystems became mounted read-only (while some heavy reading/
> writing was being performed to that filesystem).
> 
> Can anyone explain to me what is going on here, and why this is happening 
> to me about every 10 days.

I don't know why this:

>  EXT3-fs error (device sdb8): ext3_free_blocks: bit already cleared for block 1142880
>  Aborting journal on device sdb8.

is occurring.  It indicates that the filesystem metadata is corrupted.  You
should force a fsck to fix it up.  It could be a hardware problem (disk,
cable, controller, power supply, or even main memory).

>  bad: scheduling while atomic!
>  Call Trace:
>   [<c012049e>] schedule+0x68e/0x6a0

This part is caused by a minor bug.



ext3_error() sleeps, so don't call it with the lock held.


---

 25-akpm/fs/ext3/balloc.c |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff -puN fs/ext3/balloc.c~ext3-schedule-inside-lock-fix fs/ext3/balloc.c
--- 25/fs/ext3/balloc.c~ext3-schedule-inside-lock-fix	Thu Feb 19 15:37:04 2004
+++ 25-akpm/fs/ext3/balloc.c	Thu Feb 19 15:38:16 2004
@@ -239,9 +239,10 @@ do_more:
 		BUFFER_TRACE(bitmap_bh, "clear bit");
 		if (!ext3_clear_bit_atomic(sb_bgl_lock(sbi, block_group),
 						bit + i, bitmap_bh->b_data)) {
-			ext3_error (sb, __FUNCTION__,
-				      "bit already cleared for block %lu", 
-				      block + i);
+			jbd_unlock_bh_state(bitmap_bh);
+			ext3_error(sb, __FUNCTION__,
+				"bit already cleared for block %lu", block + i);
+			jbd_lock_bh_state(bitmap_bh);
 			BUFFER_TRACE(bitmap_bh, "bit already cleared");
 		} else {
 			dquot_freed_blocks++;

_

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/