From: Matthias Urlichs <smurf@smurf.noris.de>
To: linux-kernel@vger.kernel.org
Subject: RE: Blockbusting news, this is important (Re: Why are bad disk se ctors numbered strangely, and what happens to them?)
Date: Sat, 18 Oct 2003 20:06:13 +0200 [thread overview]
Message-ID: <pan.2003.10.18.18.06.12.173887@smurf.noris.de> (raw)
In-Reply-To: <785F348679A4D5119A0C009027DE33C105CDB2EF@mcoexc04.mlm.maxtor.com>
Hi, Mudama, Eric wrote:
> If current trends hold, in the next few years, hard drives are going to have
> to pick up and rewrite their data continuously to avoid signal decay on the
> media...
I expect I'd be VERY unhappy if I couldn't put a complete computer in
storage any more, and expect it to work when I turn it back on in two
months / years.
What timeframe are you talking about here anyway?
Oh well, I do remember the times when disks didn't work the next
_day_ because they developed stiction and the only way to get them to run
again was to peel off the label near the center and give the thing a
not-so-gentle push with a screwdriver... in fact we had a contest how long
an 80-MB disk would continue to work with the top off. :-)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
:mouse belt: n. See {rat belt}.
next prev parent reply other threads:[~2003-10-18 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 17:18 Mudama, Eric
2003-10-18 18:06 ` Matthias Urlichs [this message]
2003-10-20 15:54 ` Rik van Riel
2003-10-20 16:09 ` Richard B. Johnson
2003-10-20 16:24 ` Chris Friesen
2003-10-21 19:13 ` H. Peter Anvin
2003-10-20 17:49 ` John Bradford
2003-10-20 17:48 ` David Lang
2003-10-20 18:29 ` John Bradford
2003-10-21 19:10 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-10-20 16:14 Mudama, Eric
2003-10-18 16:54 Mudama, Eric
2003-10-18 18:19 ` Maciej Zenczykowski
2003-10-18 20:08 ` John Bradford
2003-10-19 22:53 ` Pavel Machek
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=pan.2003.10.18.18.06.12.173887@smurf.noris.de \
--to=smurf@smurf.noris.de \
--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
all inboxes | Powered by JetHome®