From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 26 14:05: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 56C8116A424; Wed, 26 Oct 2005 14:05:41 +0000 (GMT) (envelope-from girgen@FreeBSD.org) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id B806343D4C; Wed, 26 Oct 2005 14:05:40 +0000 (GMT) (envelope-from girgen@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by rambutan.pingpong.net (8.13.3/8.13.3) with ESMTP id j9QE5dMj023951; Wed, 26 Oct 2005 16:05:39 +0200 (CEST) (envelope-from girgen@FreeBSD.org) Date: Wed, 26 Oct 2005 16:05:39 +0200 From: Palle Girgensohn To: "Matthew N. Dodd" Message-ID: <66AA0695B4793976B82E0A75@rambutan.pingpong.net> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 14:05:41 -0000 --On onsdag, oktober 26, 2005 09.41.34 -0400 "Matthew N. Dodd" wrote: > 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. What kind of patching is required for 4.x? Any ideas or pointers? >> 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. Oh. A port would be great. :-) Any ideas on something similar for the ciss(4) controller? >> 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. You mean from /etc/syslog? That is not the problem, it seems to be some kind of timeout for every error that is the problem, I'm not sure. CPU runs at 100% constantly, anyway, but mostly running postgresql and java, not syslogd. > >> 3. Will the array rebuild automatically once they insert the new disk? > > Depends on the BIOS setting. OK, thanks. /Palle > > -- > 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.