From owner-freebsd-stable@FreeBSD.ORG  Sat Oct 12 12:59:02 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 725F321B
 for <freebsd-stable@freebsd.org>; Sat, 12 Oct 2013 12:59:02 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 46B302C58
 for <freebsd-stable@freebsd.org>; Sat, 12 Oct 2013 12:59:01 +0000 (UTC)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 57FF720C0A
 for <freebsd-stable@freebsd.org>; Sat, 12 Oct 2013 08:59:00 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute2.internal (MEProxy); Sat, 12 Oct 2013 08:59:00 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=+ZR5I+MP7YcxqrfO3hYmX/QN+X8=; b=SVB
 YrjI9uWtGrVGoHaNPQOI8S+Wsndoozuz3ezVdW9wkdvLiLT5XR69l9YYYMpwHXs7
 y/ztr4g01Rt9AhI8GaJz9CO0DEO9bIMINVfsw76h/H10LKoYdJnWrJp7cIMlM1F+
 laSr9IoUeK+MzrxWhjeObiyyEgf8B3UrnJbpDVnk=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 35BB911669B; Sat, 12 Oct 2013 08:59:00 -0400 (EDT)
Message-Id: <1381582740.22847.33156113.3132AF9C@webmail.messagingengine.com>
X-Sasl-Enc: h2asXRM1TYMt+SPKuDjk+wdlocr5BKNdPiGw6gk23v/o 1381582740
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988
In-Reply-To: <85290551-4239-495E-ACCD-9F03C20D40EF@gsoft.com.au>
References: <85290551-4239-495E-ACCD-9F03C20D40EF@gsoft.com.au>
Subject: Re: ZFS devd messages
Date: Sat, 12 Oct 2013 07:59:00 -0500
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Oct 2013 12:59:02 -0000

On Fri, Oct 11, 2013, at 19:51, Daniel O'Connor wrote:
> 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?
> 

This seems like something we should make sure is fixed before the 10.0
release. Thanks for reporting it.