From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 26 13:41:41 2005 Return-Path: X-Original-To: hardware@FreeBSD.ORG Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13E3216A41F; Wed, 26 Oct 2005 13:41:41 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [70.88.158.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CA7943D48; Wed, 26 Oct 2005 13:41:40 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [70.88.158.93]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id j9QDfYY3095396; Wed, 26 Oct 2005 09:41:39 -0400 (EDT) (envelope-from mdodd@FreeBSD.ORG) Date: Wed, 26 Oct 2005 09:41:34 -0400 (EDT) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Palle Girgensohn In-Reply-To: <8B7CFEAEC6605866DCAAF092@rambutan.pingpong.net> Message-ID: <20051026093814.U609@sasami.jurai.net> References: <8B7CFEAEC6605866DCAAF092@rambutan.pingpong.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [70.88.158.93]); Wed, 26 Oct 2005 09:41:39 -0400 (EDT) Cc: hardware@FreeBSD.ORG Subject: Re: ida problems, one disk broken = system very slow X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2005 13:41:41 -0000 On Tue, 25 Oct 2005, Palle Girgensohn wrote: > A customer has a machine with four disks in RAID 10 using the ida(8) > controller on FreeBSD-4.11. ftp://ftp.jurai.net/users/winter/idacontrol.tar would solve a few of your problems on 5.x or better but getting it to work on 4.x requires patching and recompiling. > Now one disk is broken. I have some questions: > > 1. How can I detect that a disk in a raid cluster is broken? It seems > natural to me that the raid driver would log info about a broken disk, > but I have not seen this happen with any raid controller driver. Most array drivers have a userland utility that allows inspection of array status. The utility for ida(4) isn't in the base system yet. > 2. The system is extremely slow and hardly usable right now. The > customer are still waiting for a replacement disk. Is there any way to > get the system to just ignore the broken disk instead of trying to use > it and fail. I get thousands of "ida0: soft error" in messages log. If > the system would realize that it had problems with the disk, and ignore > them, perhaps it wouldn't become unsable, Well, you could rate-limit the error messages, or comment out the message entirely. > 3. Will the array rebuild automatically once they insert the new disk? Depends on the BIOS setting. -- Lord, wheresoever this rifle goest, guide my hands upon it. Let a shot never be fired in anger or error. Bless it to your righteous service. In your mercy, Thine is the kingdom Amen.