From owner-freebsd-bugs@FreeBSD.ORG Sat Oct 26 14:20:02 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5EEE092B for ; Sat, 26 Oct 2013 14:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3FD8C2FC4 for ; Sat, 26 Oct 2013 14:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9QEK2hv063180 for ; Sat, 26 Oct 2013 14:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9QEK2wr063179; Sat, 26 Oct 2013 14:20:02 GMT (envelope-from gnats) Resent-Date: Sat, 26 Oct 2013 14:20:02 GMT Resent-Message-Id: <201310261420.r9QEK2wr063179@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Mark Felder Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D47F790A for ; Sat, 26 Oct 2013 14:16:44 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from oldred.freebsd.org (oldred.freebsd.org [8.8.178.121]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A8B392FB0 for ; Sat, 26 Oct 2013 14:16:44 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id r9QEGili091759 for ; Sat, 26 Oct 2013 14:16:44 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id r9QEGit9091755; Sat, 26 Oct 2013 14:16:44 GMT (envelope-from nobody) Message-Id: <201310261416.r9QEGit9091755@oldred.freebsd.org> Date: Sat, 26 Oct 2013 14:16:44 GMT From: Mark Felder To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: misc/183335: devd no longer matches ZFS events X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Oct 2013 14:20:02 -0000 >Number: 183335 >Category: misc >Synopsis: devd no longer matches ZFS events >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Oct 26 14:20:01 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Mark Felder >Release: >Organization: >Environment: >Description: according to -stable mailing list entry, devd doesn't come with working ZFS event matching anymore. It would be nice if the proper syntax came with the 10 RELEASE and perhaps was backported to 9.x if necessary. http://freebsd.1045724.n5.nabble.com/ZFS-devd-messages-td5851231.html In case thread is not available on nabble: ####################################### 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? ####################################### On 12/10/2013, at 11:21, Daniel O'Connor <[hidden email]> wrote: > 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? For now I nuked the entries out of /etc/devd.conf and made some in /etc/devd/zfs.conf (where they should have been to start with IMO..) like so.. notify 10 { match "system" "ZFS"; action "logger -p kern.err 'ZFS notice: type=$type version=$version class=$class pool_guid=$pool_guid vdev_guid=$vdev_guid'"; action "echo 'ZFS notice: type=$type version=$version class=$class pool_guid=$pool_guid vdev_guid=$vdev_guid' | mail -s 'ZFS Event' zfs"; }; And added an alias for zfs@. It would be nice if this was the default, yes it is a bit noisy and not very user friendly but at least you get notice something weird is happening out of the box. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: