From: "J. Hart" <jhart@atr.co.jp>
To: linux-kernel@vger.kernel.org
Cc: jhart@atr.co.jp
Subject: Re: File Corruption in Kernel 2.4.18
Date: Tue, 23 Jul 2002 11:56:04 +0900 [thread overview]
Message-ID: <3D3CC5C4.54E9EF72@atr.co.jp> (raw)
Here is a further update on the file corruption question :
I ran the DFT utility which picked up two bad sectors, which I then
repaired. A rerun of DFT after that gave no further reports of any problems. I
then tried the directory tree copy (cp -a aminet aminet1) which produced one
corrupted file at the destination. All the other destination files in the tree
(70652 files, 7.6G) appeared to be correct.
An additional rerun of the IBM DFT utility after this reported no problems
despite the corrupt copy.
In order to resolve this issue, my employer is considering the replacement
of my current machine with a new one having the following specifications :
motherboard: Asus P4T AGP Pro/4X
ram : 1Gb
OS : Linux 2.4.7-10 i686 unknown
CPU : Intel(R) Pentium(R) 4 CPU 1800MHz
Gfx : Matrox Graphics, Inc. MGA G400 AGP
drives : Seagate 40gb UATA ST340810A (two of these)
controller : Intel PIIX4 Ultra 100 Chipset
: (Intel Corporation 82801BA IDE U100)
chipset : Intel Corporation 82850 850 (Tehama) Chipset Host Bridge (MCH)
Are there any outstanding issues with machines of this new configuration as
there seemed to be with my old machine ?
With Thanks,
J. Hart
next reply other threads:[~2002-07-23 2:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 2:56 J. Hart [this message]
2002-07-23 3:04 ` File Corruption in Kernel 2.4.18 Thunder from the hill
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 4:16 Kelledin
2002-07-18 2:00 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
[not found] ` <20020718081630.GX1465@niksula.cs.hut.fi>
2002-07-22 10:10 ` Wilfried Weissmann
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=3D3CC5C4.54E9EF72@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox