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
Date: Tue, 4 Oct 2005 12:28:35 +0200 [thread overview]
Message-ID: <20051004102834.GA16755@favonius> (raw)
In-Reply-To: <20051001213655.GE6397@ime.usp.br>
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
next prev parent reply other threads:[~2005-10-04 10:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 11:10 Strange disk corruption with Linux >= 2.6.13 Rogério Brito
2005-09-27 11:34 ` Diego Calleja
2005-09-27 11:58 ` Rogério Brito
2005-09-27 12:10 ` Rogério Brito
2005-09-27 11:57 ` Grant Coady
2005-09-27 12:43 ` Ondrej Zary
2005-10-01 21:22 ` Rogério Brito
2005-09-27 14:04 ` Lennart Sorensen
2005-10-01 21:28 ` Rogério Brito
2005-10-03 16:20 ` Lennart Sorensen
[not found] ` <Pine.LNX.4.63.0509271331590.21130@alpha.polcom.net>
2005-09-27 12:20 ` Rogério Brito
2005-09-27 12:38 ` Grzegorz Kulewski
2005-09-27 19:42 ` Guennadi Liakhovetski
2005-09-27 21:01 ` Erik Mouw
2005-09-27 21:44 ` Guennadi Liakhovetski
2005-10-01 21:15 ` Rogério Brito
2005-10-08 22:35 ` Guennadi Liakhovetski
2005-10-09 9:30 ` Rogério Brito
2005-10-01 21:02 ` Rogério Brito
2005-09-27 23:31 ` Nigel Cunningham
2005-10-01 21:36 ` Rogério Brito
2005-10-02 0:06 ` Grant Coady
2005-10-03 4:17 ` Rogério Brito
2005-10-03 4:20 ` Willy Tarreau
2005-10-03 4:55 ` Nigel Cunningham
2005-10-04 10:28 ` Sander [this message]
2005-10-04 12:42 ` Nigel Cunningham
2005-09-28 8:43 ` Ville Herva
2005-09-28 23:23 ` Alan Cox
2005-09-29 6:29 ` Ville Herva
2005-09-29 16:14 ` Alan Cox
2005-10-03 5:05 ` Rogério Brito
2005-10-03 5:15 ` Rogério Brito
[not found] <4RlFC-2ev-17@gated-at.bofh.it>
[not found] ` <4Rxdq-2Tc-19@gated-at.bofh.it>
[not found] ` <4SXfs-7hM-27@gated-at.bofh.it>
2005-10-02 3:37 ` Bodo Eggert
2005-10-03 4:30 ` Rogério Brito
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=20051004102834.GA16755@favonius \
--to=sander@humilis.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
/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;
as well as URLs for NNTP newsgroup(s).