public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Gatti <marco@pianoinflames.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg KH <greg@kroah.com>, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Bug: get EXT3-fs error Allocating block in system zone
Date: Fri, 07 Dec 2007 08:11:51 +0100	[thread overview]
Message-ID: <4758F237.9060201@pianoinflames.de> (raw)
In-Reply-To: <20071206162500.1f76a234.akpm@linux-foundation.org>

Andrew Morton schrieb:
>> But the effect is under every circumstances described above that I got 
>> after an unspecific time EXT3-fs errors. I tried to use different 
>> partitions, one for root and data, got errors on both.
>>
>> Dec  3 15:05:34 adira EXT3-fs error (device sdb4): ext3_new_block: 
>> Allocating block in system zone - blocks from 74907667, length 1
>>
>> I tried different hard disks, different sizes of partitions, always the 
>> same issue. I always saw that mem is fully cached (I have 8GB RAM!). 
>> After that, the ext3 has severe faults fsck.ext3 repaired them, but an 
>> amount of data was lost.
>>
>> I also tried with different file systems (reiserfs3, xfs), also kernel 
>> trace errors, so I got back to ext3.
>>
>> Can't believe that it's a pure fs-error. Is it an ahci.c issue? Or a 
>> problem with acpi and memory management?
> 
> At a guess I'd say the disk system is being bad.  it might be a hardware
> failure too - it's a new system.
> 

I thought that first, too. I forgot to mention that I did a badblocks on 
the partitions and the two whole disks. No issues reported. I formated 
the disks several times and reinstalled the whole gentoo and compiled 
the kernel again more than one time (I tried 2.6.24-rc3 too) 'cause of 
the ext3 / other fs issues. I did dd if=/dev/zero of=... on the 
partitions and the whole disks. No issues of bad blocks. The strange 
thing is everything works fine under Windows XP x64 Prof. But I don't 
wanted to use that OS really... So I can't believe that's a hardware 
issue of the disks.

  parent reply	other threads:[~2007-12-07  7:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 20:54 Bug: get EXT3-fs error Allocating block in system zone Marco Gatti
2007-12-07  0:25 ` Andrew Morton
2007-12-07  0:42   ` Linus Torvalds
2007-12-07  7:24     ` Marco Gatti
2007-12-08 21:21     ` Marco Gatti
2007-12-09  0:47       ` Linus Torvalds
2007-12-09 16:59         ` Marco Gatti
2007-12-07  7:11   ` Marco Gatti [this message]
     [not found] <fa.Fg53DJSEh/kZhf/uRCv9FYZsaSQ@ifi.uio.no>
     [not found] ` <fa.nPzIjJ2SchPb1LOa/dRWb/WyEZU@ifi.uio.no>
     [not found]   ` <fa.LkmHGN+Fx6H930bfeCDU6pGdBKM@ifi.uio.no>
     [not found]     ` <fa.oSqMiIX7WubypXrhZGaRKU5wNGU@ifi.uio.no>
     [not found]       ` <fa.0pc9/nNmTq+eWIU9rADRn0xYGdI@ifi.uio.no>
     [not found]         ` <fa.hqM73i24f6G31R5F3sKL8+3H8Ww@ifi.uio.no>
2007-12-09 17:55           ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4758F237.9060201@pianoinflames.de \
    --to=marco@pianoinflames.de \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox