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