Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 1C6B3B5DC29 for ; Tue, 21 Jun 2011 17:11:06 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 70289-10 for ; Tue, 21 Jun 2011 20:10:59 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ey0-f174.google.com (mail-ey0-f174.google.com [209.85.215.174]) by mail.postgresql.org (Postfix) with ESMTP id E21D2B5DBD3 for ; Tue, 21 Jun 2011 17:10:58 -0300 (ADT) Received: by eyx24 with SMTP id 24so31938eyx.19 for ; Tue, 21 Jun 2011 13:10:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=toGpffCmzxOB2hlN/aW0yCgisVwIV9pRLVWmH4qq3uo=; b=F//KboDOvD0+j8+8NTcBaFe7yKDJXKaRVJxFcs6rHoMd+myVG6+KVWtpxAwfZ2usAl 8Qy1tILBxlvyrCPXaud3d0XtuSMUIlDnG1NDBEw+rxDAR4x8wJ2b+Lsoe8f6Q9Jttjcu E3L/3WX95CDIZM30NdBsMwo+hosqVthA6ylVc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=dFxeQOarWqo8Y6V2Lx9bD7Pgr+tXBvbWvdD3fd3PqOd2TfBCGahUJQCVXtMt9tx73S Wbhwq1hyIA4DZiXmrD55g9FjJZuJfACtiouhAS5eaCKOAH3l6NCFHsckKGUaOxsUWkRW 0JiBujb+DoL37jiD3PI6ugmavW8eSfmivKERk= Received: by 10.14.9.228 with SMTP id 76mr2516758eet.206.1308687058150; Tue, 21 Jun 2011 13:10:58 -0700 (PDT) Received: from [192.168.73.63] (5357DA75.cm-6-8d.dynamic.ziggo.nl [83.87.218.117]) by mx.google.com with ESMTPS id a45sm5683456eec.23.2011.06.21.13.10.56 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Jun 2011 13:10:57 -0700 (PDT) Message-ID: <4E00FABB.6030302@gmail.com> Date: Tue, 21 Jun 2011 22:10:35 +0200 From: Yeb Havinga User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Greg Smith CC: Florian Weimer , pgsql-performance@postgresql.org Subject: Re: Contemplating SSD Hardware RAID References: <4E0015F2.9060504@drivefaster.net> <4E003B44.9090005@2ndQuadrant.com> <4E004D96.7010308@gmail.com> <4E004E74.5020209@gmail.com> <82d3i777ow.fsf@mid.bfk.de> <4E00B4B9.50006@2ndQuadrant.com> In-Reply-To: <4E00B4B9.50006@2ndQuadrant.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.897 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001, URIBL_RED=0.001 X-Spam-Level: X-Archive-Number: 201106/201 X-Sequence-Number: 44134 On 2011-06-21 17:11, Greg Smith wrote: > On 06/21/2011 07:19 AM, Florian Weimer wrote: >> 3ware controllers offer SMART pass-through, and smartctl supports it. >> I'm sure there's something similar for Areca controllers. > > Depends on the model, drives, and how you access the management > interface. For both manufacturers actually. Check out > http://notemagnet.blogspot.com/2008/08/linux-disk-failures-areca-is-not-so.html > for example. There I talk about problems with a specific Areca > controller, as well as noting in a comment at the end that there are > limitations with 3ware supporting not supporting SMART reports against > SAS drives. > > Part of the whole evaluation chain for new server hardware, especially > for SSD, needs to be a look at what SMART data you can get. Yeb, I'd > be curious to get more details about what you've been seeing here if > you can share it. You have more different models around than I have > access to, especially the OCZ ones which I can't get my clients to > consider still. (Their concerns about compatibility and support from > a relatively small vendor are not completely unfounded) > This is what a windows OCZ tool explains about the different smart values (excuse for no mark up) for a Vertex 2 Pro. SMART READ DATA Revision: 10 Attributes List 1: SSD Raw Read Error Rate Normalized Rate: 120 total ECC and RAISE errors 5: SSD Retired Block Count Reserve blocks remaining: 100% 9: SSD Power-On Hours Total hours power on: 451 12: SSD Power Cycle Count Count of power on/off cycles: 61 13: SSD Soft Read Error Rate Normalized Rate: 120 100: SSD GBytes Erased Flash memory erases across the entire drive: 128 GB 170: SSD Number of Remaining Spares Number of reserve Flash memory blocks: 17417 171: SSD Program Fail Count Total number of Flash program operation failures: 0 172: SSD Erase Fail Count Total number of Flash erase operation failures: 0 174: SSD Unexpected power loss count Total number of unexpected power loss: 13 177: SSD Wear Range Delta Delta between most-worn and least-worn Flash blocks: 0 181: SSD Program Fail Count Total number of Flash program operation failures: 0 182: SSD Erase Fail Count Total number of Flash erase operation failures: 0 184: SSD End to End Error Detection I/O errors detected during reads from flash memory: 0 187: SSD Reported Uncorrectable Errors Uncorrectable RAISE errors reported to the host for all data access: 0 194: SSD Temperature Monitoring Current: 26 High: 37 Low: 0 195: SSD ECC On-the-fly Count Normalized Rate: 120 196: SSD Reallocation Event Count Total number of reallocated Flash blocks: 0 198: SSD Uncorrectable Sector Count Total number of uncorrectable errors when reading/writing a sector: 0 199: SSD SATA R-Errors Error Count Current SATA RError count: 0 201: SSD Uncorrectable Soft Read Error Rate Normalized Rate: 120 204: SSD Soft ECC Correction Rate (RAISE) Normalized Rate: 120 230: SSD Life Curve Status Current state of drive operation based upon the Life Curve: 100 231: SSD Life Left Approximate SDD life Remaining: 99% 232: SSD Available Reserved Space Amount of Flash memory space in reserve (GB): 17 235: SSD Supercap Health Condition of an external SuperCapacitor Health in mSec: 0 241: SSD Lifetime writes from host Number of bytes written to SSD: 448 GB 242: SSD Lifetime reads from host Number of bytes read from SSD: 192 GB Same tool for a Vertex 3 (not pro) SMART READ DATA Revision: 10 Attributes List 1: SSD Raw Read Error Rate Normalized Rate: 120 total ECC and RAISE errors 5: SSD Retired Block Count Reserve blocks remaining: 100% 9: SSD Power-On Hours Total hours power on: 7 12: SSD Power Cycle Count Count of power on/off cycles: 13 171: SSD Program Fail Count Total number of Flash program operation failures: 0 172: SSD Erase Fail Count Total number of Flash erase operation failures: 0 174: SSD Unexpected power loss count Total number of unexpected power loss: 10 177: SSD Wear Range Delta Delta between most-worn and least-worn Flash blocks: 0 181: SSD Program Fail Count Total number of Flash program operation failures: 0 182: SSD Erase Fail Count Total number of Flash erase operation failures: 0 187: SSD Reported Uncorrectable Errors Uncorrectable RAISE errors reported to the host for all data access: 0 194: SSD Temperature Monitoring Current: 128 High: 129 Low: 127 195: SSD ECC On-the-fly Count Normalized Rate: 100 196: SSD Reallocation Event Count Total number of reallocated Flash blocks: 0 201: SSD Uncorrectable Soft Read Error Rate Normalized Rate: 100 204: SSD Soft ECC Correction Rate (RAISE) Normalized Rate: 100 230: SSD Life Curve Status Current state of drive operation based upon the Life Curve: 100 231: SSD Life Left Approximate SDD life Remaining: 100% 241: SSD Lifetime writes from host Number of bytes written to SSD: 162 GB 242: SSD Lifetime reads from host Number of bytes read from SSD: 236 GB There's some info burried in http://archives.postgresql.org/pgsql-performance/2011-03/msg00350.php where two Vertex 2 pro's are compared; the first has been really hammered with pgbench, the second had a few months duty in a workstation. The raw value of SSD Available Reserved Space seems to be a good candidate to watch to go to 0, since the pgbenched-drive has 16GB left and the workstation disk 17GB. Would be cool to graph with e.g. symon (http://i.imgur.com/T4NAq.png) -- Yeb Havinga http://www.mgrid.net/ Mastering Medical Data