From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 14 23:41:22 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8C9716A4CE; Wed, 14 Jan 2004 23:41:22 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ECBD43D5C; Wed, 14 Jan 2004 23:41:21 -0800 (PST) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.9/8.12.9) with ESMTP id i0F7fKdi029892; Thu, 15 Jan 2004 02:41:20 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Thu, 15 Jan 2004 02:41:20 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Message-ID: <20040115022720.G90982@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: ida(4) driver: Compaq Smart Array users wanted. X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2004 07:41:22 -0000 Using an up to date -CURRENT and ftp://ftp.jurai.net/users/winter/idacontrol.tar the status of a logical volume may be displayed, and rebuilds initiated from a running system. I'm not at all happy with the output formatting of the utility but its better than nothing. Any feedback will be appreciated etc. Additionaly, I'd be very interested to know if anyone else can reproduce some of the problems I've observed with the ida(4) driver when hotswapping drives. I've been able to lock up the controller reliablly by removing and inserting a failed drive. I've tested against against the following controllers: SMART-2/P SMART-2SL Smart Array 3200 I'm running firmware version 4.50 (SP18018) on all controllers; older firmware displayed an even wider variety of weird problems, though some were likely related to my test platform (an old Proliant 850R). In most cases the lockup will cause the driver to panic as an impossible value is returned from the done() function. I've got code that fixes the panic and uses a watchdog timeout to catch the actual hang but this really isn't very useful as my system lives entirely on the RAID. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00