Date: Mon, 25 Nov 2013 14:47:33 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: "Daniel O'Connor" <doconnor@gsoft.com.au>, freebsd-stable stable <freebsd-stable@FreeBSD.org> Subject: Re: ZFS devd messages Message-ID: <529346E5.4070900@FreeBSD.org> In-Reply-To: <85290551-4239-495E-ACCD-9F03C20D40EF@gsoft.com.au> References: <85290551-4239-495E-ACCD-9F03C20D40EF@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
on 12/10/2013 03:51 Daniel O'Connor said the following:
> Hi,
> It seems that the ZFS messages no longer match entries in devd.conf, eg..
> notify 10 {
> match "system" "ZFS";
> match "type" "vdev";
> action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'";
> };
>
> Doesn't match anything because messages now look like..
> Processing event '!system=ZFS subsystem=ZFS type=resource.fs.zfs.removed version=0 class=resource.fs.zfs.removed pool_guid=469710819 vdev_guid=215223839'
>
> Does anyone have an updated set of rules handy?
I've come up with the following change:
http://people.freebsd.org/~avg/devd-zfs.diff
I will appreciate any testing and reviews.
Thanks!
--
Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?529346E5.4070900>