From owner-freebsd-current@FreeBSD.ORG Tue Jan 20 18:29:16 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFEB3106564A for ; Tue, 20 Jan 2009 18:29:16 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 507758FC13 for ; Tue, 20 Jan 2009 18:29:16 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n0KITE4U072324; Tue, 20 Jan 2009 19:29:14 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n0KITE8V072323; Tue, 20 Jan 2009 19:29:14 +0100 (CET) (envelope-from olli) Date: Tue, 20 Jan 2009 19:29:14 +0100 (CET) Message-Id: <200901201829.n0KITE8V072323@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, josh.carroll@gmail.com In-Reply-To: <8cb6106e0901200641x4b0bda9ag31e6f059f13035a7@mail.gmail.com> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 20 Jan 2009 19:29:14 +0100 (CET) Cc: Subject: Re: SATA DMA errors on second ICH10 bus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, josh.carroll@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 18:29:17 -0000 Josh Carroll wrote: > I've got 2 WD black drives on order to replace these two ST31000340AS, > and originally my intention was to use them for separate filesystems, > but I think I'll gmirror them now, to be safe(er). Some people recommend to use different vendors for the components of disk mirrors, in order to reduce the likelihood that both drives will fail at about the same time due to a firmware bug or similar. That advice seems to be particularly valuable given the current firmware problems that particular Seagate disks are exhibiting. For example, I've got these in a server: # atacontrol list | grep ad Master: ad0 Serial ATA II Master: ad1 Serial ATA v1.0 # diskinfo ad0 ad1 ad0 512 160041885696 312581808 310101 16 63 ad1 512 160041885696 312581808 310101 16 63 # gmirror status Name Status Components mirror/gm0 COMPLETE ad0 ad1 Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "anyone new to programming should be kept as far from C++ as possible; actually showing the stuff should be considered a criminal offence" -- Jacek Generowicz