From: Thunder from the hill <thunder@ngforever.de>
To: Daniel Egger <degger@fhm.edu>
Cc: Anton Altaparmakov <aia21@cantab.net>,
Thunder from the hill <thunder@ngforever.de>, <venom@sns.it>,
<linux-kernel@vger.kernel.org>
Subject: Re: IBM Desktar disk problem?
Date: Fri, 5 Jul 2002 10:57:01 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0207051053120.10105-100000@hawkeye.luckynet.adm> (raw)
In-Reply-To: <1025883147.17269.24.camel@sonja.de.interearth.com>
Hi,
On 5 Jul 2002, Daniel Egger wrote:
> Though the timespan makes me curious: Why is there a magnitude
> difference in runtime between the first problem on a fresh drive
> and after a lowlevel format?
Can be anything. The disk's administration parts getting messed up with
crap, and already having got messed up by some test run right after
production. Or maybe the drives were padded with maintainer data before
they were shipped (means, after production).
Imagine it thermodynamically. A half-ordered system keeps getting messed
up. Somewhen it's messed up. If you order your system it will take longer
for the drive to get messed up.
Maybe the part which failed in the old firmware was some garbage
collection code? Something that removes the crap?
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2002-07-05 16:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 10:27 IBM Desktar disk problem? venom
2002-07-05 10:40 ` Jens Axboe
2002-07-05 10:50 ` Anton Altaparmakov
2002-07-05 12:36 ` Jens Axboe
2002-07-05 13:27 ` venom
2002-07-05 14:15 ` Tomas Konir
2002-07-05 14:26 ` Jens Axboe
2002-07-05 14:48 ` Tomas Konir
2002-07-05 15:38 ` Daniel Egger
2002-07-05 15:42 ` Tomas Konir
2002-07-05 20:11 ` Matthias Andree
2002-07-05 20:21 ` Tomas Konir
2002-07-05 20:39 ` Matthias Andree
2002-07-05 20:50 ` Tomas Konir
2002-07-05 22:58 ` Matthias Andree
[not found] ` <Pine.LNX.4.44L0.0207052216410.3293-100000@moje.ich.vabo.cz >
2002-07-05 21:05 ` Anton Altaparmakov
2002-07-05 21:08 ` Tomas Konir
2002-07-07 12:46 ` Timo Jantunen
2002-07-11 15:14 ` Thunder from the hill
2002-07-10 16:15 ` Bill Shirley
2002-07-10 17:09 ` Matthias Andree
2002-07-05 23:00 ` Mohammad A. Haque
2002-07-05 12:50 ` Daniel Egger
2002-07-05 14:03 ` Thunder from the hill
2002-07-05 13:50 ` Zwane Mwaikambo
2002-07-05 15:18 ` Bartlomiej Zolnierkiewicz
2002-07-05 16:58 ` Thunder from the hill
2002-07-05 15:23 ` Daniel Egger
2002-07-05 20:23 ` Matthias Andree
[not found] ` <Pine.LNX.4.44.0207050801190.10105-100000@hawkeye.luckynet. adm>
2002-07-05 14:29 ` Anton Altaparmakov
2002-07-05 15:32 ` Daniel Egger
2002-07-05 16:57 ` Thunder from the hill [this message]
2002-07-09 13:23 ` Bill Davidsen
2002-07-09 20:35 ` Daniel Egger
2002-07-05 15:04 Randal, Phil
2002-07-05 18:01 Voluspa
2002-07-05 18:05 ` Bartlomiej Zolnierkiewicz
2002-07-05 18:19 ` Voluspa
2002-07-11 19:29 Iain Thomas
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=Pine.LNX.4.44.0207051053120.10105-100000@hawkeye.luckynet.adm \
--to=thunder@ngforever.de \
--cc=aia21@cantab.net \
--cc=degger@fhm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=venom@sns.it \
/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.