mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xuan Baldauf <xuan--lkml@baldauf.org>
To: Peter Horton <pdh@colonel-panic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1-pre8 losing pages
Date: Fri, 26 Jan 2001 03:28:39 +0100	[thread overview]
Message-ID: <3A70E0D7.8D28F8B6@baldauf.org> (raw)
In-Reply-To: <20010125231659.A2128@colonel-panic.com>



Peter Horton wrote:

> I'm experiencing repeatable corruption whilst writing large volumes of
> data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon on an
> ASUS A7V (VIA KT133 chipset) motherboard 128M RAM (tested with 'memtest86'
> for 10 hours).
>
> First, I realised that the fsck was noticing small corruptions on my ext2
> volume. My first suspect was the much discussed VIA IDE controller. As a
> test I created a 128M file from "urandom" and copied it to twenty six
> files. When I MD5 the files one or two of them are usually corrupt. The
> damage usually occurs in the 24th copy (thought not always). Inspecting
> the files shows a single 4K block (aligned on a 4K boundary) that is
> completely different from what it should be. The kernel logs no errors
> whilst writing the corrupt files.
>
> I've repeated the test on the other on-board IDE controller (Promise), a
> different hard disk, and on reiserfs. I see the corruption in all cases.
>
> I tried building the kernel for "Pentium-Classic", and I tried a few older
> kernels (2.4.0-test5 and 2.4.0-test12), still bad (all kernels built with
> GCC 2.95.2 - Debian potato).
>
> I really could do with some help as where to look next :-). I did try and
> come up with a test to see whether bad data is written or whether the
> damaged piece is just not written, but if I alter the testing procedure
> too much the problem seems to go away. It seems to just lose a single page
> under one very specific circumstance.

So what output does following bash script produce?

#!/bin/bash
uname -a
dd if=/dev/urandom of=test0 bs=1024k count=128
I=1
while test $I -lt 32; do
  echo $I
  cp test0 test$I
  I="$(($I+1))"
done
md5sum test*

I cannot reproduce your behaviour in 2.4.1-pre9.

Xuân.

>
>
> P.
>
> ( configs attached )
>
>   ------------------------------------------------------------
>                   Name: info.tar.gz
>    info.tar.gz    Type: Unix Tape Archive (application/x-tar)
>               Encoding: base64
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-26  2:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 23:16 Peter Horton
2001-01-26  2:28 ` Xuan Baldauf [this message]
     [not found] ` <3A70DEF1.80ECEF80@baldauf.org>
2001-01-26  9:24   ` Peter Horton
2001-01-26 19:46     ` Peter Horton
2001-01-26 19:48       ` Russell King
2001-01-28 12:11         ` Peter Horton
2001-01-28 16:33           ` Andre Hedrick

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=3A70E0D7.8D28F8B6@baldauf.org \
    --to=xuan--lkml@baldauf.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdh@colonel-panic.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

all inboxes | Powered by JetHome®