From owner-freebsd-stable@FreeBSD.ORG Thu Feb 15 10:09:40 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41BC216A468 for ; Thu, 15 Feb 2007 10:09:40 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id C2D3913C4A7 for ; Thu, 15 Feb 2007 10:09:39 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (nspslg@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l1FA9Xat028795; Thu, 15 Feb 2007 11:09:38 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l1FA9XZU028794; Thu, 15 Feb 2007 11:09:33 +0100 (CET) (envelope-from olli) From: Oliver Fromme Message-Id: <200702151009.l1FA9XZU028794@lurza.secnetix.de> To: harry@schmalzbauer.de (Harald Schmalzbauer) Date: Thu, 15 Feb 2007 11:09:33 +0100 (CET) In-Reply-To: <200702151035.33807.harry@schmalzbauer.de> X-Mailer: ELM [version 2.5 PL8] 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]); Thu, 15 Feb 2007 11:09:38 +0100 (CET) Cc: freebsd-stable@freebsd.org Subject: Re: gmirror or ata problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 10:09:40 -0000 Harald Schmalzbauer wrote: > I think this is a problem when the internal thermal recalibration takes too > long. > Consumer HDDs can be "offline" quiet some time, I don't have numbers handy, > but see Western Digitals explanation on their SATA RE (RaidEdition) Drives. > Again, no link handy, sorry. That was certainly not the cause of the problem. First, the drives aren't "consumer" ones; they're specifically for server usage and 24h availability. Second, the problem affected only one drive out of four identical ones (two machines with two drives each in a gmirror configuration). The other three drives never had any problems whatsoever. As I wrote recently, we replaced that drive and hadn't had any problems since. So it was indeed a hardware problem with that particular drive ... And what ever kind of problem it was, FreeBSD didn't seem to be able to report it properly. 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 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard." -- Peter van der Linden