Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 3DD111337B47 for ; Fri, 22 Apr 2011 11:04:36 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 22052-07 for ; Fri, 22 Apr 2011 14:04:18 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailhub1.renesys.com (mailhub1.ep.renesys.com [195.160.236.248]) by mail.postgresql.org (Postfix) with ESMTP id 78B66133798E for ; Fri, 22 Apr 2011 11:04:18 -0300 (ADT) Received: from ops05.psm1.renesys.com (ops05.psm1.renesys.com [10.200.1.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhub1.renesys.com (Postfix) with ESMTP id F40D0671A4 for ; Fri, 22 Apr 2011 14:04:17 +0000 (UTC) Received: (from rouilj@localhost) by ops05.psm1.renesys.com (8.13.8/8.13.8/Submit) id p3ME4HS1022039 for pgsql-performance@postgresql.org; Fri, 22 Apr 2011 14:04:17 GMT Date: Fri, 22 Apr 2011 14:04:17 +0000 From: John Rouillard To: postgres performance list Subject: OT (slightly) testing for data loss on an SSD drive due to power failure Message-ID: <20110422140417.GU27218@renesys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201104/316 X-Sequence-Number: 43378 Hi all: I realize this is slightly off topic, but is an issue of concern with the use of ssd's. We are setting up a storage server under solaris using ZFS. We have a couple of ssd's 2 x 160GB Intel X25-M MLC SATA acting as the zil (write journal) and are trying to see if it is safe to use for a power fail situation. Our testing (10 runs) hasn't shown any data loss, but I am not sure our testing has been running long enough and is valid, so I hoped the people here who have tested an ssd for data loss may have some guidance. The testing method is to copy a bunch of files over NFS to the server with the zil. When the copy is running along, pull the power to the server. The NFS client will stop and if the client got a message that block X was written safely to the zil, it will continue writing with block x+1. After the server comes backup and and the copies resume/finish the files are checksummed. If block X went missing, the checksums will fail and we will have our proof. We are looking at how to max out the writes to the SSD on the theory that we need to fill the dram buffer on the SSD and get it saturated enough such that it can't flush data to permanent storage as fast as the data is coming in. (I.E. make it a writeback with a longer delay so it's more likely to drop data.) Does anybody have any comments or testing methodologies that don't involve using an actual postgres instance? Thanks for your help. -- -- rouilj John Rouillard System Administrator Renesys Corporation 603-244-9084 (cell) 603-643-9300 x 111