public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RE:Re: ide drive dying?
Date: 07 Sep 2002 14:03:38 +0200	[thread overview]
Message-ID: <1031400218.12089.9.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <1031346090.10612.90.camel@irongate.swansea.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

Am Fre, 2002-09-06 um 23.01 schrieb Alan Cox:

> Thats up to the owner. There are lots of uses for such drives - /tmp,
> swap, in a raid array, etc

Having two of such notorious broken drives in a RAID array is also
not an option in many cases. Mirroring is meant to increase data
security in case a drive fails spontaneously; using particularly bad
drives for that purpose is a way to work against the reason.

> Mind you I collect drives that have nice properties like "hangs the
> entire scsi bus when inserted into an SCA connector" for testing with

You probably should keep a DeathStar as the worst drive ever made.
Heck, if my latest replacement drive from IBM ("serviceable used part")
starts failing again I might as well ship it to you instead of IBM.
 
-- 
Servus,
       Daniel

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2002-09-07 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 20:40 RE:Re: ide drive dying? Hell.Surfers
2002-09-06 21:01 ` Alan Cox
2002-09-06 21:45   ` jbradford
2002-09-07  1:02   ` Jason L Tibbitts III
2002-09-07 12:03   ` Daniel Egger [this message]
2002-09-06 21:07 ` DevilKin
  -- strict thread matches above, loose matches on Subject: below --
2002-09-07 23:51 Hell.Surfers
2002-09-08  0:17 ` Andre Hedrick
2002-09-08  3:03 Hell.Surfers
2002-09-08  4:25 ` 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=1031400218.12089.9.camel@sonja.de.interearth.com \
    --to=degger@fhm.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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