The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks not in datazone
@ 2005-09-05 16:24 Riccardo Castellani
  2005-09-05 18:20 ` Stephen C. Tweedie
  0 siblings, 1 reply; 3+ messages in thread
From: Riccardo Castellani @ 2005-09-05 16:24 UTC (permalink / raw)
  To: linux-kernel

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.
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 !
I have this message:

Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8): ext3_free_blocks: 
Freeing blocks not in datazone - block = 134217728, count = 1
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
Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8) in ext3_truncate: 
Journal has aborted
Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8) in 
ext3_reserve_inode_write: Journal has aborted
Sep  5 17:34:40 mrtg kernel: ext3_abort called.
Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8): 
ext3_journal_start_sb: Detected aborted journal
Sep  5 17:34:40 mrtg kernel: Remounting filesystem read-only
Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8) in ext3_orphan_del: 
Journal has aborted
Sep  5 17:34:40 mrtg kernel: EXT3-fs error (device hda8) in 
ext3_reserve_inode_write: Journal has aborted

Riccardo


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks not in datazone
  2005-09-05 16:24 EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks not in datazone Riccardo Castellani
@ 2005-09-05 18:20 ` Stephen C. Tweedie
  2005-09-06  6:52   ` EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocksnot " Riccardo Castellani
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen C. Tweedie @ 2005-09-05 18:20 UTC (permalink / raw)
  To: Riccardo Castellani; +Cc: Stephen Tweedie, linux-kernel

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
> 


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocksnot in datazone
  2005-09-05 18:20 ` Stephen C. Tweedie
@ 2005-09-06  6:52   ` Riccardo Castellani
  0 siblings, 0 replies; 3+ messages in thread
From: Riccardo Castellani @ 2005-09-06  6:52 UTC (permalink / raw)
  To: Stephen C. Tweedie, Riccardo Castellani; +Cc: Stephen Tweedie, linux-kernel

I run memtest86 and It gives errors.
I removed the installed 256 MB RAM of 512 MB and now PC works.

thanks


----- Original Message ----- 
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>
Sent: Monday, September 05, 2005 8:20 PM
Subject: Re: EXT3-fs error (device hda8): ext3_free_blocks: Freeing 
blocksnot in datazone


> 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
>>
> 


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-09-06  6:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-05 16:24 EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks not in datazone Riccardo Castellani
2005-09-05 18:20 ` Stephen C. Tweedie
2005-09-06  6:52   ` EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocksnot " Riccardo Castellani

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox