Date: Tue, 4 Oct 2005 12:28:35 +0200
From: Sander <sander@humilis.net>
To: Nigel Cunningham <ncunningham@cyclades.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Message-ID: <20051004102834.GA16755@favonius>
Reply-To: sander@humilis.net
References: <20050927111038.GA22172@ime.usp.br> <1127863912.4802.52.camel@localhost> <20051001213655.GE6397@ime.usp.br>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051001213655.GE6397@ime.usp.br>
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1268
Lines: 32

Rog?rio Brito wrote (ao):
> On Sep 28 2005, Nigel Cunningham wrote:
> > 3) Is the corruption only ever in memory, or seen on disk too?
> 
> I have noticed the problem mostly on disk. One strange situation was
> when I was untarring a kernel tree (compressed with bzip2) and in the
> middle of the extraction, bzip2 complained that the thing was
> corrupted.
> 
> I removed what was extracted right away and tried again to extract the
> tree (at this point, suspecting even that something in software had
> problems). The problem with bzip2 occurred again. Then, I rebooted the
> system an the problem magically went away.

That would mean the corruption existed in memory only. The kernel
tarball got sucked into memory and got corrupted. On reboot, the tarball
gets read in again, and this time no corruption. The on disk tarball was
oke it seems.

If you run memtest86+ (latest version) for at least 24 hours it _should_
find something.

	Kind regards, Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/