From owner-freebsd-stable@FreeBSD.ORG Thu Nov 24 23:13:31 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 130A816A8B5 for ; Thu, 24 Nov 2005 23:13:31 +0000 (GMT) (envelope-from kama@pvp.se) Received: from ms1.as.pvp.se (dns.pvp.se [213.64.187.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59C0B454AD for ; Thu, 24 Nov 2005 22:07:44 +0000 (GMT) (envelope-from kama@pvp.se) Received: by ms1.as.pvp.se (Postfix, from userid 1001) id C447FBD; Thu, 24 Nov 2005 23:08:28 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ms1.as.pvp.se (Postfix) with ESMTP id BF845BB; Thu, 24 Nov 2005 23:08:28 +0100 (CET) Date: Thu, 24 Nov 2005 23:08:28 +0100 (CET) From: kama X-X-Sender: kama@ns1.as.pvp.se To: Holger Kipp In-Reply-To: <20051124183412.GA50476@intserv.int1.b.intern> Message-ID: <20051124230726.G63444@ns1.as.pvp.se> References: <20051123033644.O1053@ganymede.hub.org> <4385FFED.3050003@crc.u-strasbg.fr> <20051124181507.GA3012@serverbitch.de> <20051124183412.GA50476@intserv.int1.b.intern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, Sascha Holzleiter Subject: Re: ciss(4) driver in FreeBSD 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 23:13:33 -0000 On Thu, 24 Nov 2005, Holger Kipp wrote: > On Thu, Nov 24, 2005 at 07:15:07PM +0100, Sascha Holzleiter wrote: > > > > On Thu, Nov 24, 2005 at 07:01:17PM +0100, Philippe Pegon wrote: > > > We have about thirty HP servers (DL360 and DL380) with FreeBSD 5 and 6, > > > and they seem to work fine with ciss driver. Just this damn bug > > > (kern/83375) which is not related to ciss driver... > > > > do you know of any method to monitor these [ciss] controllers with FreeBSD, > > e.g. to detect drive failures? > > You could simply monitor the corresponding ciss syslog-messages > and scan for state changes (ie from OK to something else). Apart > from reboot-messages, you only get messages if states are > changing... Maybe this is what you are looking for? http://people.freebsd.org/~jcagle/ /Bjorn