Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFrVZ-0005qd-DL for pgsql-performance@arkaria.postgresql.org; Wed, 13 Mar 2013 19:38:41 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UFrVY-0002BO-Q7 for pgsql-performance@arkaria.postgresql.org; Wed, 13 Mar 2013 19:38:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFrVX-0002BI-4t for pgsql-performance@postgresql.org; Wed, 13 Mar 2013 19:38:39 +0000 Received: from wsip-70-169-168-7.pn.at.cox.net ([70.169.168.7] helo=fs.denninger.net) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFrVT-0005qn-QZ for pgsql-performance@postgresql.org; Wed, 13 Mar 2013 19:38:38 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fs.denninger.net (8.14.6/8.13.1) with ESMTP id r2DJcWIS020638 for ; Wed, 13 Mar 2013 14:38:32 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Wed Mar 13 14:38:32 2013 Message-ID: <5140D5B3.7080104@denninger.net> Date: Wed, 13 Mar 2013 14:38:27 -0500 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Steve Crawford CC: pgsql-performance@postgresql.org Subject: Re: New server setup References: <4D6D1410-2208-4DAA-BD64-69BE1FD94E55@autouncle.com> <513CADB7.4030803@2ndQuadrant.com> <51409C51.1070601@kickstone.com> <38D48FB0-92A8-433B-8D34-4C63738B45BA@gmail.com> <5140A623.20005@kickstone.com> <5140D226.4060609@pinpointresearch.com> In-Reply-To: <5140D226.4060609@pinpointresearch.com> X-Enigmail-Version: 1.5.1 Content-Type: multipart/alternative; boundary="------------010308080309050900000103" X-Antivirus: avast! (VPS 130313-0, 03/13/2013), Outbound message X-Antivirus-Status: Clean X-Pg-Spam-Score: -0.9 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org This is a multi-part message in MIME format. --------------010308080309050900000103 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by fs.denninger.net id r2DJcWIS020638 On 3/13/2013 2:23 PM, Steve Crawford wrote: > On 03/13/2013 09:15 AM, John Lister wrote: >> On 13/03/2013 15:50, Greg Jaskiewicz wrote: >>> SSDs have much shorter life then spinning drives, so what do you do >>> when one inevitably fails in your system ? >> Define much shorter? I accept they have a limited no of writes, but >> that depends on load. You can actively monitor the drives "health" >> level... > > What concerns me more than wear is this: > > InfoWorld Article: > http://www.infoworld.com/t/solid-state-drives/test-your-ssds-or-risk-ma= ssive-data-loss-researchers-warn-213715 > > > Referenced research paper: > https://www.usenix.org/conference/fast13/understanding-robustness-ssds-= under-power-fault > > > Kind of messes with the "D" in ACID. > > Cheers, > Steve One potential way around this is to run ZFS as the underlying filesystem and use the SSDs as cache drives. If they lose data due to a power problem it is non-destructive. Short of that you cannot use a SSD on a machine where silent corruption is unacceptable UNLESS you know it has a supercap or similar IN THE DISK that guarantees that on-drive cache can be flushed in the event of a power failure. A battery-backed controller cache DOES NOTHING to alleviate this risk. If you violate this rule and the power goes off you must EXPECT silent and possibly-catastrophic data corruption. Only a few (and they're expensive!) SSD drives have said protection. If yours does not the only SAFE option is as I described up above using them as ZFS cache devices. --=20 -- Karl Denninger /The Market Ticker =AE/ Cuda Systems LLC --------------010308080309050900000103 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 3/13/2013 2:23 PM, Steve Crawford wrote:
On 03/13/2013 09:15 AM, John Lister wrote:
On 13/03/2013 15:50, Greg Jaskiewicz wrote:
SSDs have much shorter life then spinning drives, so what do you do when one inevitably fails in your system ?
Define much shorter? I accept they have a limited no of writes, but that depends on load. You can actively monitor the drives "health" level...

What concerns me more than wear is this:

InfoWorld Article:
http://www.infoworld.com/t/solid-state-drives/test-your-ssds-or-risk-massive-data-loss-researchers-warn-213715

Referenced research paper:
https://www.usenix.org/conference/fast13/understanding-robustness-ssds-under-power-fault

Kind of messes with the "D" in ACID.

Cheers,
Steve

One potential way around this is to run ZFS as the underlying filesystem and use the SSDs as cache drives.  If they lose data due to a power problem it is non-destructive.

Short of that you cannot use a SSD on a machine where silent corruption is unacceptable UNLESS you know it has a supercap or similar IN THE DISK that guarantees that on-drive cache can be flushed in the event of a power failure.  A battery-backed controller cache DOES NOTHING to alleviate this risk.  If you violate this rule and the power goes off you must EXPECT silent and possibly-catastrophic data corruption.

Only a few (and they're expensive!) SSD drives have said protection.  If yours does not the only SAFE option is as I described up above using them as ZFS cache devices.

--
-- Karl Denninger
The Market Ticker ®
Cuda Systems LLC
--------------010308080309050900000103--