Date: Fri, 3 Oct 2014 20:54:40 +0300 From: Mikolaj Golub <to.my.trociny@gmail.com> To: Matt Churchyard <matt.churchyard@userve.net> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: HAST with broken HDD Message-ID: <20141003175439.GA7664@gmail.com> In-Reply-To: <97aab72e19d640ebb65c754c858043cc@SERVER.ad.usd-group.com> References: <542BC135.1070906@Skynet.be> <542BDDB3.8080805@internetx.com> <CA%2BdUSypO8xTR3sh_KSL9c9FLxbGH%2BbTR9-gPdcCVd%2Bt0UgUF-g@mail.gmail.com> <542BF853.3040604@internetx.com> <CA%2BdUSyp4vMB_qUeqHgXNz2FiQbWzh8MjOEFYw%2BURcN4gUq69nw@mail.gmail.com> <542C019E.2080702@internetx.com> <CA%2BdUSyoEcPdJ1hdR3k1vNROFG7p1kN0HB5S2a_0gYhiV75OLAw@mail.gmail.com> <542C0710.3020402@internetx.com> <CA%2BdUSyr9OK9SvN3wX-O4DeriLBP-EEuAA8TTSYwdGfcR1asdtQ@mail.gmail.com> <97aab72e19d640ebb65c754c858043cc@SERVER.ad.usd-group.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 01, 2014 at 03:51:43PM +0000, Matt Churchyard wrote: > HAST is basically "RAID1-over-network", so if a disk fails, it > should just handle read/writes using the other disk, and the > filesystem on top, be it UFS/ZFS/whatever, should just carry on as > normal (which is what has been observed). Of course, HAST (or the > OS) should notify you of the disk error though (probably through > devd) so you can do something about it. Maybe it already exists, but > HAST should be able to provide overall status information and raise > events just like ZFS or any RAID subsystem would. You also of course > shouldn't get scrub errors and corruption like that seen in the > original post either just because one half of the HAST mirror has > gone. Disk errors are recorded to syslog. Also error counters are displayed in `hastctl list' output. There is snmp_hast(3) in base -- a module for bsnmp to retrieve this statistics via snmp protocol (traps are not supported though). For notifications, the hastd can be configured to execute an arbitrary command on various HAST events (see description for `exec' in hast.conf(5)). Unfortunately, it does not have hooks for I/O error events currently. It might be worth adding though. The problem with this that it may generate to many events, so some throttling is needed. -- Mikolaj Golub
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141003175439.GA7664>