All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Thunder from the hill <thunder@ngforever.de>
Cc: venom@sns.it, linux-kernel@vger.kernel.org
Subject: Re: IBM Desktar disk problem?
Date: 05 Jul 2002 17:23:39 +0200	[thread overview]
Message-ID: <1025882620.17269.15.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207050801190.10105-100000@hawkeye.luckynet.adm>

Am Fre, 2002-07-05 um 16.03 schrieb Thunder from the hill:

> ...and tell all the people who got a DTLA (because it's not as expensive 
> as others in some countries, mind France, USA, Germany) to drop their 
> disks if they want to use Linux, because we're too lazy to find a 
> solution. That might be cool to you, but we want HARDWARE SUPPORT for 
> Linux! That's why we're here.
 
> There _is_ a solution, we just have to find it.

Except you believe in the at least questionable explanation from IBM 
there's nothing one can solve with software. And since quite a lot
of drives died under several Linux, Windows, *BSD and Mac versions
I don't buy the driver argument and in fact think that IBM is using
this poor excuse to avoid a big (and expensive) replacement plan
on the cost of the users.

I've yet to see a <insert your favourite non-IBM harddrive manufacturer
here>-drive dying after a few months of use, the negative record in this
regard (except for the IBMs) was a Quantum Atlas UW-SCSI drive (which
was in fact also manufactured FOR IBM) which died after 2,5 years of
heavy use which is at least somewhere in the range what one might expect
as lifetime; all other drives here (up to 10 years old) are still alive
and kickin'.

Even if you have backups and RAID systems, a broken harddrive can be
quite expensive; think of data restoration, drive replacement,
downtimes, shipment, data loss which all costs at least one thing: time
and lots of it. 

We estimate around 10h per broken drive while it takes a lot less time
(<1h) to simple replace the discs before the accident which is what
we're doing now with all IBM drives prophylactically.

-- 
Servus,
       Daniel


  parent reply	other threads:[~2002-07-05 15:34 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 [this message]
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
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=1025882620.17269.15.camel@sonja.de.interearth.com \
    --to=degger@fhm.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder@ngforever.de \
    --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.