From owner-freebsd-hardware@FreeBSD.ORG  Tue Oct 25 12:46:54 2005
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
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 95E3F16A420
	for <hardware@FreeBSD.org>; Tue, 25 Oct 2005 12:46:54 +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 DCF6043D55
	for <hardware@FreeBSD.org>; Tue, 25 Oct 2005 12:46:53 +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 j9PCkpTc088409
	for <hardware@freebsd.org>; Tue, 25 Oct 2005 14:46:51 +0200 (CEST)
	(envelope-from girgen@FreeBSD.org)
Date: Tue, 25 Oct 2005 14:46:51 +0200
From: Palle Girgensohn <girgen@FreeBSD.org>
To: hardware@FreeBSD.org
Message-ID: <8B7CFEAEC6605866DCAAF092@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: 
Subject: 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 <freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2005 12:46:54 -0000

Hi!

A customer has a machine with four disks in RAID 10 using the ida(8) 
controller on FreeBSD-4.11.

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.

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,

3. Will the array rebuild automatically once they insert the new disk?

/Palle