Skip to contentSkip to conversation

EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks not in datazone

DISCUSSION Riccardo Castellani 2 participants 3 messages Sep 5, 2005 – Sep 6, 2005

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

Hi,

Quoted 6 lines · Riccardo Castellani

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.

Quoted 3 lines
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

...

Quoted 2 lines

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

Quoted 1 line
#2 lore raw

Re: EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocksnot in datazone

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" <[email protected]>
To: "Riccardo Castellani" <[email protected]>
Cc: "Stephen Tweedie" <[email protected]>; "linux-kernel" <[email protected]>
Sent: Monday, September 05, 2005 8:20 PM
Subject: Re: EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocksnot in datazone

Quoted 28 lines

Hi,

Quoted 6 lines · Riccardo Castellani

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.

Quoted 3 lines
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

...

Quoted 2 lines

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

Quoted 1 line