Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 60F57B5DBD6 for ; Tue, 19 Jul 2011 07:35:57 -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 66776-01 for ; Tue, 19 Jul 2011 10:35:51 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ey0-f171.google.com (mail-ey0-f171.google.com [209.85.215.171]) by mail.postgresql.org (Postfix) with ESMTP id 048BDB5DBC8 for ; Tue, 19 Jul 2011 07:35:50 -0300 (ADT) Received: by eye22 with SMTP id 22so3102479eye.16 for ; Tue, 19 Jul 2011 03:35:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=ptzGfxpkQZC52vfS7qHvPmVab9En8dCmOhwn8OxWOCk=; b=waP7Fb/BC8Y9sFoaPecEUpz6xPdVSqSuuUkahM3sm9JtWZDvvvT6PsHTTJiPegr0+J zcK18iroo2OjXTaScfaFzXiXI/UnFnGFt1LhaHRn3rbyWvWMRSoy2ijWjOSD8sSaa9KU sU3O0kr0LJKVFYlNCnx7NmGB39vRhcUspi0cw= Received: by 10.213.96.135 with SMTP id h7mr2705691ebn.128.1311071750498; Tue, 19 Jul 2011 03:35:50 -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 x4sm2639827eef.21.2011.07.19.03.35.48 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Jul 2011 03:35:49 -0700 (PDT) Message-ID: <4E255DF9.20005@gmail.com> Date: Tue, 19 Jul 2011 12:35:37 +0200 From: Yeb Havinga User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Florian Weimer CC: Andy , pgsql-performance@postgresql.org Subject: Re: BBU still needed with SSD? References: <1310953399.25726.YahooMailClassic@web111304.mail.gq1.yahoo.com> <4E23E72B.2070508@gmail.com> <82vcuyd7p5.fsf@mid.bfk.de> In-Reply-To: <82vcuyd7p5.fsf@mid.bfk.de> 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.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001 X-Spam-Level: X-Archive-Number: 201107/190 X-Sequence-Number: 44402 On 2011-07-19 09:56, Florian Weimer wrote: > * Yeb Havinga: > >> The biggest drawback of 2 SSD's with supercap in hardware raid 1, is >> that if they are both new and of the same model/firmware, they'd >> probably reach the end of their write cycles at the same time, thereby >> failing simultaneously. > I thought so too, but I've got two Intel 320s (I suppose, the report > device model is "SSDSA2CT040G3") in a RAID 1 configuration, and after > about a month of testing, one is down to 89 on the media wearout > indicator, and the other is still at 96. Both devices are > deteriorating, but one at a significantly faster rate. That's great news if this turns out to be generally true. Is it on mdadm software raid? I searched a bit in the mdadm manual for reasons this can be the case. It isn't the occasional check (echo check > /sys/block/md0/md/sync_action) since that seems to do two reads and compare. Another idea was that the layout of the mirror might not be different, but the manual says that the --layout configuration directive is only for RAID 5,6 and 10, but not RAID 1. Then my eye caught --write-behind, the maximum number of outstanding writes and it has a non-zero default value, but is only done if a drive is marked write-mostly. Maybe it is caused by the initial build of the array? But then a 7% difference seems like an awful lot. It would be interesting to see if the drives also show total xyz written, and if that differs a lot too. regards, Yeb Havinga