From: David Boreham <david_list@boreham.org>
To: pgsql-performance@postgresql.org
Subject: Re: Reports from SSD purgatory
Date: Wed, 24 Aug 2011 13:43:00 -0600
Message-ID: <4E555444.1090601@boreham.org> (raw)
In-Reply-To: <d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.com>
References: <4E49B0A0.2060705@2ndQuadrant.com>
<201108241848.061232@ms14.lnh.mail.rcn.net>
<d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.com>
On 8/24/2011 1:32 PM, Tomas Vondra wrote:
> Why is that important? It's simply a failure of electronics and it has
> nothing to do with the wear limits. It simply fails without prior
> warning from the SMART.
In the cited article (actually in all articles I've read on this
subject), the failures were not properly analyzed*.
Therefore the conclusion that the failures were of electronics
components is invalid.
In the most recent article, people have pointed to it as confirming
electronics failures
but the article actually states that the majority of failures were
suspected to be
firmware-related.
We know that a) there have been failures, but b) not the cause.
We don't even know for sure that the cause was not cell wear.
That's because all we know is that the drives did not report
wear before failing. The wear reporting mechanism could be broken for
all we know.
--
*A "proper" analysis would involve either the original manufacturer's FA
lab, or a qualified independent analysis lab.
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: <4E555444.1090601@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