From: Marco Gatti <marco@pianoinflames.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.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: Sat, 08 Dec 2007 22:21:27 +0100 [thread overview]
Message-ID: <475B0AD7.10500@pianoinflames.de> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712061631510.13796@woody.linux-foundation.org>
Linus Torvalds schrieb:
>
> But the disk errors are something else, doesn't ring a bell. Sounds like
> IO corruption on the group descriptor block or something like that. Might
> be worth testing to see if the problem goes away with less than 4GB of
> RAM..
>
Today, I tested with different amounts of RAM:
2 GB: everything works fine
4 GB: same issue as described before with allocating block in system zone
So what to do, in order to use more than 2 Gigs of RAM?
Marco
next prev parent reply other threads:[~2007-12-08 21:21 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 [this message]
2007-12-09 0:47 ` Linus Torvalds
2007-12-09 16:59 ` Marco Gatti
2007-12-07 7:11 ` Marco Gatti
[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=475B0AD7.10500@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