From: David Boreham <david_list@boreham.org>
To: pgsql-performance@postgresql.org
Subject: Re: Reports from SSD purgatory
Date: Mon, 15 Aug 2011 22:13:51 -0600
Message-ID: <4E49EE7F.3000305@boreham.org> (raw)
In-Reply-To: <4E49B0A0.2060705@2ndQuadrant.com>
References: <4E49B0A0.2060705@2ndQuadrant.com>
<dons flameproof underpants once more...>
This comment by the author I think tends to support my theory that most
of the
failures seen are firmware related (and not due to actual hardware
failures, which
as I mentioned in the previous thread are very rare and should occur
roughly equally
often in hard drives as SSDs) :
/As we explained in the article, write endurance is a spec'ed failure.
That won't happen in the first year, even at enterprise level use. That
has nothing to do with our data. We're interested in random failures.
The stuff people have been complaining about... BSODs with OCZ drives,
LPM stuff with m4s, the SSD 320 problem that makes capacity disappear...
etc... Mostly "soft" errors. Any hard error that occurs is subject to
the "defective parts per million" problem that any electrical component
also suffers from./
and from the main article body:
/Firmware is the most significant, and we see its impact in play almost
every time an SSD problem is reported.
/
(Hard drives also suffer from firmware bugs of course)
I think I'm generally encouraged by this article because it suggests
that once the firmware bugs are fixed (or if you buy from a vendor less
likely to ship with bugs in the first place), then SSD reliability will
be much better than it is perceived to be today.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: david_list@boreham.org
Subject: Re: Reports from SSD purgatory
In-Reply-To: <4E49EE7F.3000305@boreham.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox