All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Thomas Fjellstrom <tfjellstrom@strangesoft.net>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: failed command FLUSH CACHE EXT
Date: Thu, 03 Jun 2010 10:23:06 +0200	[thread overview]
Message-ID: <4C07666A.7000705@gmail.com> (raw)
In-Reply-To: <201006021742.32232.tfjellstrom@strangesoft.net>

Hello,

On 06/03/2010 01:42 AM, Thomas Fjellstrom wrote:
> I seem to have rather bad luck with hard drives. Every time I buy more than 
> two, I tend to get one or two failures out of the batch. 25-50% failure rate 
> almost. Horrible. I at least average 1 dead hard drive a year since I got my 
> first computer.

Hmmm... that sounds really high.  Out of how many?  Hard drives do
fail sometimes but not that easily even if you put it under relatively
heavy use 24/7.  Maybe there is a common cause - say, instable power,
vibration, impact or whatever?  Or maybe the universe just doesn't
like you?  :-)

Thanks.

-- 
tejun

  reply	other threads:[~2010-06-03  8:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-30  2:46 via 8237 sata errors Thomas Fjellstrom
2010-05-30 18:40 ` Robert Hancock
2010-05-30 18:57   ` Thomas Fjellstrom
2010-05-30 19:33     ` Thomas Fjellstrom
2010-05-30 19:40       ` Robert Hancock
2010-05-30 19:48         ` Thomas Fjellstrom
2010-05-31  1:19           ` Thomas Fjellstrom
2010-06-02 21:10             ` failed command FLUSH CACHE EXT (was: Re: via 8237 sata errors) Thomas Fjellstrom
2010-06-02 23:05               ` Robert Hancock
2010-06-02 23:42                 ` Thomas Fjellstrom
2010-06-03  8:23                   ` Tejun Heo [this message]
2010-06-03  8:41                     ` failed command FLUSH CACHE EXT Thomas Fjellstrom

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=4C07666A.7000705@gmail.com \
    --to=htejun@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tfjellstrom@strangesoft.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.