From: "David Rees" <drees76@gmail.com>
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 16:22:17 -0800 [thread overview]
Message-ID: <72dbd3150901191622k6b57cfd1pf7e156f5a80144f4@mail.gmail.com> (raw)
In-Reply-To: <20090120002923.065f24ca@diego-desktop>
On Mon, Jan 19, 2009 at 3:29 PM, Diego Calleja <diegocg@gmail.com> wrote:
> 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? It's
> still not clear if the firmware update is safe (some affected but
> working drives are dying after the firmware update), so some people
> like me is still waiting (and hoping that the drive doesn't die) for
> more stable firmware updates...
What would blacklisting these buggy drives achieve? There isn't
anything that can be done except warn the user that they have known
buggy firmware and let them know they should contact the vendor for a
firmware update. But until that bug hits, it doesn't seem to
otherwise affect the performance or functionality of the drives.
-Dave
next prev parent reply other threads:[~2009-01-20 0:25 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 [this message]
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
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=72dbd3150901191622k6b57cfd1pf7e156f5a80144f4@mail.gmail.com \
--to=drees76@gmail.com \
--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®