Date: Thu, 24 Nov 2005 20:15:41 +0100 From: Philippe Pegon <Philippe.Pegon@crc.u-strasbg.fr> To: Holger Kipp <hk@alogis.com> Cc: freebsd-stable@freebsd.org, Sascha Holzleiter <sascha@daemonground.de> Subject: Re: ciss(4) driver in FreeBSD 6.x ... Message-ID: <4386115D.5070702@crc.u-strasbg.fr> In-Reply-To: <20051124183412.GA50476@intserv.int1.b.intern> References: <20051123033644.O1053@ganymede.hub.org> <4385FFED.3050003@crc.u-strasbg.fr> <20051124181507.GA3012@serverbitch.de> <20051124183412.GA50476@intserv.int1.b.intern>
next in thread | previous in thread | raw e-mail | index | archive | help
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... you could also use camcontrol(8) for example : camcontrol inquiry da0 -D > > Regards, > Holger Kipp > alogis AG, Berlin -- Philippe Pegon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4386115D.5070702>