daily_status_zfs_enable="yes"
Checking status of graid(8) devices:
Name Status Components
raid/r0 OPTIMAL ada1 (ACTIVE (ACTIVE))
ada0 (ACTIVE (ACTIVE))
Checking status of graid(8) devices:
Name Status Components
raid/r0 DEGRADED ada0 (ACTIVE (ACTIVE))
"|IFS=' '&&p=/usr/local/bin/procmail&&test -f $p&&exec $p -Yf-||exit 75"
I found that there is similar daemon on Linux - zed:I don't think there's anything out-of-the-box in FreeBSD base system (yet) - there's zfsd(8), but the man page says it simply logs the messages about events to syslog (as compared to e.g. Fault Manager in illumos where it has snmp/smtp notifications).
These go toI found that there is similar daemon on Linux - zed:
devd
on FreeBSD. See zpool-events(8). # zpool offline build ada1p9.elip2
Processing event '!system=ZFS subsystem=ZFS type=resource.fs.zfs.statechange version=0 class=resource.fs.zfs.statechange pool=build [etc.etc.etc.]
That's cool, I didn't know it existed. A few years ago I started a prototype "ZFS watcher", which was a small script that ran once an hour and sent an e-mail whenever the zpool status was "not perfect". It worked for a while, but it had hard-coded into it what the perfect zpool status should be (zpool A shall have two disks, and their names shall be A_1 and A_2, zpool B shall have one disk ...). I stopped using it when the configuration changed, because I was too lazy.I don't think there's anything out-of-the-box in FreeBSD base system (yet) - there's zfsd(8), but the man page says it simply logs the messages about events to syslog (as compared to e.g. Fault Manager in illumos where it has snmp/smtp notifications).