Re: hard drive problem



Aragorn wrote (in part):

IDE hard disks are intended to be used only about 8 hours per day, with
about 2 hours in total during that 8-hour timespan of being under heavy
load.

SCSI hard disks are intended to be up 24/7, with about 80% of that time
being under heavy load. Their MTBF - I know, it's just a number - is
usually around 1'000'000 hours, which boils down to about 138 years under
continuous service.

I tend to believe the MTTF number. MTBF is not important, since you never
get a second failure as hard drives are not reparable anymore. But most
people do not seem to know what MTTF is. Assuming 1 million hour MTTF, if
you have 138 hard drives in your system, you will be averaging a failure per
year.

My personal advice would be this... *Always* make backups, regardless of
the type of hard disks you're using, and regardless of whether they're used
as standalone disks or in RAID arrays. Use SCSI disks for systems that
require a standalone disk - e.g. because you can't afford two SCSI disks -
in a mission-critical environment - with the word "mission-critical" in a
very subjective context.

I am not sure about this. My big machine has 4 SCSI hard drives and 2 EIDE
drives. I already have 2 more SCSI drives on hand to replace the EIDE ones,
but I am too busy to change them. Changing the hardware is pretty simple,
but I want to move some partitions around, and one of them is the boot
drive, so that is somewhat harder, so I am putting it off (still). I think I
will change them when my kitchen remodelling project is complete.

Most people find SCSI far too expensive. So plainly and simply, buy IDE
disks and use RAID. They're dirt-cheap these days, so best is to make use
of it while you can...

I would rather use SCSI drives because I do not want to bother with RAID,
and because I want to know what is on each drive for optimization of seeks
and transfers when running IBM's DB2 dbms. But I recognize that what one
does with the hard drives depends critically on what one plans to do with
the entire system.

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 06:40:01 up 13 days, 15:48, 3 users, load average: 4.82, 4.63, 4.46
.



Relevant Pages

  • Re: libata in 2.4.24?
    ... As a result SCSI disks are reliable for database ... if the OS driver has not issued a FLUSH CACHE ... I hope you mean the drives don't report completion until the data is on ...
    (Linux-Kernel)
  • Re: MicroVAX 3500 questions
    ... DSSI nor SCSI, ... It's an inconvenience but the system will boot without it. ... etc are disks ... The RA7x drives are about the size of an RD54. ...
    (comp.sys.dec)
  • Re: 3B2 Disks
    ... 2 MFM drives on a custom controller. ... But a friend had a 3B2 which had a SCSI interface, ... tablets around for erasing disks. ... But -- the 3B2 was the porting base for unix for some time. ...
    (comp.sys.3b1)
  • SUMMARY SCSI Disk Errors - sense key: not ready
    ... Possible reasons for the disk problems included high humidity, power supply ... problems, dying motor, poor cabling and a problem with the SCSI interface to ... I suspect the drives' motors were slowly dying; I replaced both disks one ...
    (SunManagers)
  • Re: How do I find equipment (drives of various types) for my 6-year-old Linux system?
    ... > I would have thought that an 80-pin SCSI drive wouldn't work on my system! ... If you currently have 68-pin drives, ... Or has IDE improved in that area? ... SCSI's big advantage is that you can connect multiple disks more easily ...
    (comp.os.linux.hardware)