From: Valdis.Kletnieks@vt.edu
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Faulty seagate drives, are going to be blacklisted?
Date: Mon, 19 Jan 2009 22:32:25 -0500 [thread overview]
Message-ID: <85346.1232422345@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 20 Jan 2009 00:29:23 +0100." <20090120002923.065f24ca@diego-desktop>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Tue, 20 Jan 2009 00:29:23 +0100, Diego Calleja said:
> Tech sites are reporting everywhere a massive flaw in seagate drives that
> can lock up the drive and make it unusable (the bios doesn't detect it, you
> can't read the data). Haven't read anything about it here on the lists.
> Seagate has ack'ed the problem:
> http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
>
> So, apparently there're a lot of drives on the market (including mine)
> that can die any day. Are those drives going to be blacklisted?
The $64 question is, of course: What exactly should the operating system
*do* if it detects one of these drives? Prohibit it from bricking later
by essentially bricking it *now*? What if the drive already has a lot of
production data on it?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-01-20 3:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 23:29 Diego Calleja
2009-01-20 0:22 ` David Rees
2009-01-20 2:55 ` Robert Hancock
2009-01-20 15:26 ` Diego Calleja
2009-01-21 0:30 ` Robert Hancock
2009-01-20 3:32 ` Valdis.Kletnieks [this message]
2009-01-20 15:30 ` Diego Calleja
2009-01-20 17:24 ` Valdis.Kletnieks
2009-01-20 18:18 ` Diego Calleja
2009-01-21 10:27 ` Patrick Horn
2009-01-25 1:12 ` Tejun Heo
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=85346.1232422345@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=diegocg@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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
all inboxes | Powered by JetHome®