From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 18 19:37:23 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 80050FDC; Fri, 18 Jan 2013 19:37:23 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [188.252.31.196]) by mx1.freebsd.org (Postfix) with ESMTP id D44CC202; Fri, 18 Jan 2013 19:37:22 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id r0IJbL4R013072; Fri, 18 Jan 2013 20:37:21 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id r0IJbKeL013069; Fri, 18 Jan 2013 20:37:20 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Fri, 18 Jan 2013 20:37:20 +0100 (CET) From: Wojciech Puchar To: Scott Long Subject: Re: IBM blade server abysmal disk write performances In-Reply-To: <1358533136.41693.YahooMailNeo@web120302.mail.ne1.yahoo.com> Message-ID: References: <1358529778.71931.YahooMailNeo@web120304.mail.ne1.yahoo.com> <1358533136.41693.YahooMailNeo@web120302.mail.ne1.yahoo.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2456600518-1385782499-1358537841=:13066" X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Fri, 18 Jan 2013 20:37:21 +0100 (CET) Cc: "freebsd-hackers@freebsd.org" , Dieter BSD , "gibbs@FreeBSD.org" , "scottl@FreeBSD.org" , "mjacob@FreeBSD.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 19:37:23 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2456600518-1385782499-1358537841=:13066 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT >> disk would write data >> > > I suspect that I'm encountering situations right now at netflix where this advice is not true.  I have drives that are seeing intermittent errors, then being forced into reset after a timeout, and then coming back up with filesystem problems.  It's only a suspicion at this point, not a confirmed case. true. I just assumed that anywhere it matters one would use gmirror. As for myself - i always prefer to put different manufacturers drives for gmirror or at least - not manufactured at similar time. 2 fails at the same moment is rather unlikely. Of course - everything is possible so i do proper backups to remote sites. Remote means another city. --2456600518-1385782499-1358537841=:13066--