From owner-freebsd-stable@FreeBSD.ORG Thu Nov 24 18:34:47 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 40BAC16A42C for ; Thu, 24 Nov 2005 18:34:47 +0000 (GMT) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 167A443DAC for ; Thu, 24 Nov 2005 18:34:21 +0000 (GMT) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.1/8.13.1) with ESMTP id jAOIYC3o050626; Thu, 24 Nov 2005 19:34:12 +0100 (CET) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.1/8.13.1/Submit) id jAOIYCZY050625; Thu, 24 Nov 2005 19:34:12 +0100 (CET) (envelope-from hk) Date: Thu, 24 Nov 2005 19:34:12 +0100 From: Holger Kipp To: Sascha Holzleiter Message-ID: <20051124183412.GA50476@intserv.int1.b.intern> References: <20051123033644.O1053@ganymede.hub.org> <4385FFED.3050003@crc.u-strasbg.fr> <20051124181507.GA3012@serverbitch.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051124181507.GA3012@serverbitch.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org 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 18:34:47 -0000 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... Regards, Holger Kipp alogis AG, Berlin