public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: Billy.Harvey@thrillseeker.net (Billy Harvey)
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: ide drive dying?
Date: Fri, 6 Sep 2002 19:00:11 +0100 (BST)	[thread overview]
Message-ID: <200209061800.g86I0CO9004896@darkstar.example.net> (raw)
In-Reply-To: <1031328893.16365.243.camel@rhino> from "Billy Harvey" at Sep 06, 2002 12:14:53 PM

> On Fri, 2002-09-06 at 11:42, Mike Dresser wrote:
> > On 6 Sep 2002, Alan Cox wrote:
> > 
> > > On Fri, 2002-09-06 at 16:26, Mike Dresser wrote:
> > > > eBAY, and buy yourself a new drive.  You can pickup 80 gig drives for
> > > > around 80 bucks nowadays.  I used to recommend Maxtors, until they said
> > > > they're cutting their warranty to one year from three.  I don't know what
> > > > to use anymore.
> > >
> > > At current drive density and reliabilities - raid. Software raid setups
> > > are so cheap there is little point not running RAID on IDE nowdays
> > >
> > Well, I was looking more on the side of the Windows PC's here at the
> > office, it's a bit expensive to start running raid on those.
> > 
> > Mike
> 
> Well, I haven't examined this empirically, but as the quantity of disk
> drives in an organization continues increasing, so does the probability
> of disk failure, any one of which can mean lost time/money, etc.  Drive
> reliability is likely not increasing at the same rate that density is,
> so the likelihood of lost data is probably increasing.  Since LAN speeds
> continue to increase, it might start making sense now in clusters of
> more than a few machines to make each machine less reliant on its own
> disk storage (to the point of not at all other than big swap space) and
> use the LAN more.  On the LAN put the money into a quality shared
> resource - a heavy duty UPS'd, etc. RAID system.  Especially if a RAID
> system is as easy to build/maintain/use as Alan alludes to (don't know -
> never built one).

A RAID array isn't a universal solution to all disk related problems, though, is it?  I mean, we were talking about buggy firmware earlier on in this thread - if a drive which is part of an array returns corrupted data, without acknowledging it, then you'll read corrupted data from the RAID array.  Also, an array of unreliable drives doesn't make a reliable array.

Now that the Smart Suite S.M.A.R.T. applications are unmaintained, would there be any chance of implementing S.M.A.R.T. in to the kernel IDE code?  I know the IDE code is already a nightmare, but it would be a nice feature.  S.M.A.R.T. is terribly under used at the moment - most people don't even know what it is.  Infact, I could be wrong, but isn't a subset of S.M.A.R.T. implemented on modern SCSI disks, too?

Monitoring of any kind is always a nice feature to have...

John.

  parent reply	other threads:[~2002-09-06 17:49 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 15:13 ide drive dying? DevilKin
2002-09-06 15:26 ` Mike Dresser
2002-09-06 15:39   ` Alan Cox
2002-09-06 15:42     ` Mike Dresser
2002-09-06 16:14       ` Billy Harvey
2002-09-06 16:41         ` Mike Dresser
2002-09-06 18:00         ` jbradford [this message]
2002-09-06 17:58           ` Mike Dresser
2002-09-06 15:44   ` Richard B. Johnson
2002-09-06 16:19     ` Craig Ruff
2002-09-06 17:28   ` Daniel Egger
2002-09-06 15:36 ` jbradford
2002-09-06 15:55   ` DevilKin
2002-09-06 17:22     ` jbradford
2002-09-06 19:22       ` DevilKin
2002-09-07  9:30         ` Anders Fugmann
2002-09-07  9:37           ` Udo A. Steinberg
2002-09-07 15:54           ` Holger Lubitz
2002-09-07 16:31             ` jbradford
2002-09-07 12:31         ` Daniel Egger
2002-09-07 13:08           ` jbradford
2002-09-07 13:50             ` Daniel Egger
2002-09-07 15:02               ` jbradford
2002-09-07 20:19                 ` Daniel Egger
2002-09-07 20:41                   ` jbradford
2002-09-07 21:41                     ` Alan Cox
2002-09-07 21:41                   ` Alan Cox
2002-09-07 22:00                     ` jbradford
2002-09-07 23:19                       ` David Forrest
2002-09-08 10:56                         ` Henning P. Schmiedehausen
2002-09-08 14:14                           ` jbradford
2002-09-09 21:59                             ` Alan Cox
2002-09-07 22:05                   ` Andre Hedrick
2002-09-07  7:08     ` Andre Hedrick
2002-09-06 15:37 ` mbs
2002-09-06 15:54   ` Alan Cox
2002-09-06 15:38 ` Alan Cox
2002-09-06 17:33   ` Daniel Egger
2002-09-06 20:31     ` Alan Cox
2002-09-06 15:44 ` mbs
2002-09-06 17:46 ` mbs
2002-09-06 20:32   ` Alan Cox
2002-09-07 12:34     ` Daniel Egger
2002-09-07  7:02 ` Andre Hedrick
2002-09-07  7:42   ` jbradford
2002-09-07  7:50     ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-09-06 20:40 Hell.Surfers
2002-09-06 21:01 ` Alan Cox
2002-09-07  1:02   ` Jason L Tibbitts III
     [not found] <Pine.LNX.4.33.0209062017230.14523-100000@coffee.psychology.mcmaster.ca>
2002-09-07  6:09 ` jbradford
2002-09-08  0:02 Dieter Nützel
2002-09-08 17:42 ` jbradford
2002-09-09  1:31   ` Nuitari
2002-09-08 19:27     ` Ed Sweetman
2002-09-08 20:11       ` jbradford
2002-09-09  2:37         ` Nuitari
2002-09-09 12:26   ` Joachim Breuer
2002-09-09 18:17   ` Thunder from the hill
2002-09-09 18:55     ` Mike Dresser
2002-09-10 12:48   ` Ookhoi
2002-09-10 13:59     ` Mike Dresser
2002-09-10 14:56       ` jbradford
2002-09-10 15:21         ` Mike Dresser
2002-09-10 15:29           ` Larry McVoy
2002-09-10 20:21     ` 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=200209061800.g86I0CO9004896@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=Billy.Harvey@thrillseeker.net \
    --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