mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: rtilley@vt.edu (rtilley)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hard Disk Failure
Date: Mon, 27 Jan 2003 19:56:09 +0000 (GMT)	[thread overview]
Message-ID: <200301271956.h0RJu9Ij001336@darkstar.example.net> (raw)
In-Reply-To: <3E3B3FF0@zathras> from "rtilley" at Jan 26, 2003 09:33:11 PM

> > no.  e2fsprogs might cause data loss, but not
> > physical damage.
> 
> This reminds me of something I read once.
> 
> In his book, Takedown, Tsutomu Shimomura (forgive me if that's
> spelled wrong) wrote a few short paragraphs about how he was able to
> move the head-arm of a magnetic disk drive back and forth with
> software commands. He could tell the head-arm to go to any cylinder
> on the drive, he wondered what would happen if he tried to send it
> to a cylinder that was outside the physical limits of the drive. He
> told the drive (a 200 cylinder drive) to goto cylinder 4000. The
> drive actually tried to go to that cylinder and caused a hardware
> failure in the process.

It's actually possible to make some old mainframe hard disks 'walk'
across the floor, by doing various seeks across the disk :-).

> Is it still possible for software to damage hardware in this fashion
> or is hardware smarter now? Do drives know not to try and access a
> cylinder that is outside their physical limits?

Since modern hard disks are not accessed by their physical
geometries', I would imagine that it would be rare to be able to cause
physical damage to a disk by sending a reference to an out of range
sector.  The disk has to translate the sector you send to it in to
it's real geometry anyway, so there should be no way to translate an
invalid sector in to an invalid physical geometry location, which it
could then not seek to.

John

  parent reply	other threads:[~2003-01-27 19:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27  2:33 rtilley
2003-01-27 11:09 ` Lionel Bouton
2003-01-27 19:56 ` John Bradford [this message]
2003-01-27 21:14   ` Richard B. Johnson
     [not found] <Pine.LNX.4.44.0301242353230.14696-100000@coffee.psychology.mcmaster.ca>
2003-01-27  1:36 ` Arindam Dey
2003-01-27 19:58   ` John Bradford
  -- strict thread matches above, loose matches on Subject: below --
2003-01-25  0:59 Arindam Dey

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=200301271956.h0RJu9Ij001336@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtilley@vt.edu \
    /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

Powered by JetHome