From: "J. Hart" <jhart@atr.co.jp>
To: linux-kernel@vger.kernel.org
Subject: Re: File Corruption in Kernel 2.4.18
Date: Sun, 21 Jul 2002 11:52:28 +0900 [thread overview]
Message-ID: <3D3A21EC.5000400@atr.co.jp> (raw)
In-Reply-To: 3D367295.2010109@gmx.at
I must apologize for the delay in replying to the many helpful
responses I received on this problem, and I'd like to say "thank you
very much" (Domo Arigato Gozaimasu) to the many who looked into this on
my behalf....:-)
Here's the status so far:
I ran the e2fcsk utility which did not detect any problems on the
hard drive. I had not known about the IBM DFT utility until it was
suggested by one of the responses, so I picked that up and tried it. I
ran the quick test, which immediately indicated two corrupt sectors. I
ran the Corrupt Sector Repair Utility (which does not seem to be
documented in the manual that comes with DFT) after backing up, and
repeated the tests a couple of times. There were no more complaints
from DFT. I will be reloading my test directory, which I had to dump
before the backup, and I will repeat the copy test on Monday after that
to see if the file corruption still occurs.
I do not know what caused the corrupted sectors, but I am giving
serious thought to a new mother board (to get rid of the chipset and
Promise controller), and perhaps a replacement for the "IBM DeathStar".
I'll let you all know the outcome of the tests on Monday. I am still
curious about the precise 4k damaged blocks.
next prev parent reply other threads:[~2002-07-21 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 2:00 File Corruption in Kernel 2.4.18 J. Hart
2002-07-18 3:11 ` Kelledin
2002-07-18 7:21 ` Ville Herva
2002-07-18 7:47 ` Wilfried Weissmann
2002-07-21 2:52 ` J. Hart [this message]
[not found] ` <20020718081630.GX1465@niksula.cs.hut.fi>
2002-07-22 10:10 ` Wilfried Weissmann
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 4:16 Kelledin
2002-07-23 2:56 J. Hart
2002-07-23 3:04 ` Thunder from the hill
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=3D3A21EC.5000400@atr.co.jp \
--to=jhart@atr.co.jp \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.