Date: Fri, 25 Nov 2005 11:10:47 +0100 From: Sascha Holzleiter <sascha@daemonground.de> To: freebsd-stable@freebsd.org Subject: Re: ciss(4) driver in FreeBSD 6.x ... Message-ID: <20051125101047.GA11963@serverbitch.de> In-Reply-To: <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> <20051124230726.G63444@ns1.as.pvp.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, thanks for the input on this. On Thu, Nov 24, 2005 at 11:08:28PM +0100, kama wrote: > > > 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... This is what is done already but I always wanted to watch the drives directly. The camcontrol approach seems to satisfy this. > Maybe this is what you are looking for? > > http://people.freebsd.org/~jcagle/ Also looks promising, I'll definitly try the hpasmcli util and hope there is more to it than the screenshot is showing :) Thanks, -- Sascha
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051125101047.GA11963>