Subject: Re: EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks
	not in datazone
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Riccardo Castellani <r.castellani@usl6.toscana.it>
Cc: Stephen Tweedie <sct@redhat.com>,
       linux-kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <007b01c5b236$5b6019d0$1f01a8c0@Ric>
References: <007b01c5b236$5b6019d0$1f01a8c0@Ric>
Content-Type: text/plain
Message-Id: <1125944400.1910.19.camel@sisko.sctweedie.blueyonder.co.uk>
Mime-Version: 1.0
Date: Mon, 05 Sep 2005 19:20:01 +0100
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1186
Lines: 33

Hi,

On Mon, 2005-09-05 at 17:24, Riccardo Castellani wrote:
> I'm using FC3 with Kernel 2.6.12-1.1376.
> After few hours file system on /dev/hda8 EXT3 partition has a problem so it 
> remounted in only read mode.

> Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8): ext3_free_blocks: 
> Freeing blocks not in datazone - block = 134217728, count = 1

That block number is 0x8000000 in hex.  It's a single-bit flip error;
that strongly sounds like hardware, and I'd run memtest86 on that box
next.

> Sep  5 17:34:40 mrtg kernel: Aborting journal on device hda8.
> Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8) in 
> ext3_reserve_inode_write: Journal has aborted
...

> I tried several times to run fsck on this partition and I also tried to 
> remount fs in a new partition, but it happened nothing !

What do you mean?  fsck found nothing wrong?  remount failed?  You _did_
unmount before fscking, did you?

--Stephen
> 

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