From owner-freebsd-fs@FreeBSD.ORG Mon Aug 25 06:29:57 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F8C316A4BF for ; Mon, 25 Aug 2003 06:29:57 -0700 (PDT) Received: from mail.wolves.k12.mo.us (duey.wolves.k12.mo.us [207.160.214.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECA1F43FB1 for ; Mon, 25 Aug 2003 06:29:55 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 1F64F1FF69; Mon, 25 Aug 2003 08:29:55 -0500 (CDT) Received: from mail.wolves.k12.mo.us ([127.0.0.1]) by localhost (duey.wolves.k12.mo.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19620-02-35; Mon, 25 Aug 2003 08:29:44 -0500 (CDT) Received: by mail.wolves.k12.mo.us (Postfix, from userid 1001) id 924971FEB7; Mon, 25 Aug 2003 08:29:44 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 909281B710; Mon, 25 Aug 2003 08:29:44 -0500 (CDT) Date: Mon, 25 Aug 2003 08:29:44 -0500 (CDT) From: Chris Dillon To: Tony Holmes In-Reply-To: <20030824090439.A95597@crosswinds.net> Message-ID: <20030825080957.S19707@duey.wolves.k12.mo.us> References: <20030822101702.A73928@crosswinds.net> <20030824002334.E7724@duey.wolves.k12.mo.us> <20030824090439.A95597@crosswinds.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at wolves.k12.mo.us cc: freebsd-fs@FreeBSD.ORG Subject: Re: RAID 1+0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2003 13:29:57 -0000 On Sun, 24 Aug 2003, Tony Holmes wrote: > Aye, it's hot swap LVD scsi on an internally terminated backplane. Are you sure? I've never seen an internally terminated hot-swap backplane, probably because it helps prevent foot-shooting. It wouldn't surprise me if someone does make one, though. > Ot the two drives that dropped, one will no longer spin up and the > other has a massive media error right in the middle of the platter. I recall that several of the drives that fell out of the array I was looking at had become physically damaged (wouldn't spin up and/or be recognized at all). The rest of them that dropped out without any apparent reason were physically OK, but the lack of proper termination probably caused enough errors to force the RAID controller to drop the drive. Those drives are still running today and with proper termination they haven't given any trouble. I have to wonder if the lack of termination can physically damage a drive given enough time (and a heavy load, as it was), or if it was just coincidental that we had some physically damaged drives in the midst of the termination problem. -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest and most stable server OS on the planet - Available for IA32, IA64, PC98, Alpha, and UltraSPARC architectures - x86-64, PowerPC, ARM, MIPS, and S/390 under development - http://www.freebsd.org No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced.