Date: Thu, 24 Nov 2005 19:34:12 +0100 From: Holger Kipp <hk@alogis.com> To: Sascha Holzleiter <sascha@daemonground.de> Cc: freebsd-stable@freebsd.org Subject: Re: ciss(4) driver in FreeBSD 6.x ... Message-ID: <20051124183412.GA50476@intserv.int1.b.intern> In-Reply-To: <20051124181507.GA3012@serverbitch.de> References: <20051123033644.O1053@ganymede.hub.org> <4385FFED.3050003@crc.u-strasbg.fr> <20051124181507.GA3012@serverbitch.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051124183412.GA50476>