From sacadmin Tue Feb 28 16:44:29 2006 Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca.SFBay.Sun.COM [129.145.154.35]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id k210iSIQ022399 for ; Tue, 28 Feb 2006 16:44:28 -0800 (PST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.175.66]) by sfbaymail1sca.SFBay.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k210iSTe029007 for ; Tue, 28 Feb 2006 16:44:28 -0800 (PST) Received: from poptart.sfbay.sun.com (poptart.SFBay.Sun.COM [129.146.228.147]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id k210iSIQ022396 for ; Tue, 28 Feb 2006 16:44:28 -0800 (PST) Received: from poptart.sfbay.sun.com (localhost [127.0.0.1]) by poptart.sfbay.sun.com (8.13.5+Sun/8.13.5) with ESMTP id k210i4R7184109; Tue, 28 Feb 2006 16:44:04 -0800 (PST) Received: (from mws@localhost) by poptart.sfbay.sun.com (8.13.5+Sun/8.13.5/Submit) id k210i4pF184108; Tue, 28 Feb 2006 16:44:04 -0800 (PST) From: Michael Shapiro Message-Id: <200603010044.k210i4pF184108@poptart.sfbay.sun.com> Subject: PSARC 2006/139 FMA for ZFS To: psarc@sac.eng.sun.com Date: Tue, 28 Feb 2006 16:44:04 -0800 (PST) Cc: mws@sun.com, eric.schrock@sun.com X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Status: RO Content-Length: 1340 This case introduces a set of ZFS FMA events that are produced when ZFS detects device errors, and a corresponding fmd(1M) plug-in to process these events. An FMA portfolio has been submitted and reviewed for this feature. This case seeks binding for a Micro release (ZFS is being backported to a Solaris 10 Update). As the case defines new FMA events and straightforwardly extends the previous model, and has been reviewed by members of the FMA Events C-team and ZFS team, the case is being filed as Closed Approved Automatic. If any ARC members have questions or believe the case is above the automatic approval threshold, please let us know. Exported Interface Stability ------------------------- --------- FMA ZFS Events Sun Private /usr/lib/fm/fmd/plugins/zfs-diagnosis.so Project Private /usr/lib/fm/fmd/plugins/zfs-diagnosis.conf Project Private Imported Interface PSARC Stability ------------------------- -------- --------- FMA Event Protocol 2002/412 Sun Private /usr/include/fm/fmd_api.h 2003/089 Contracted Consolidation Private The Event definitions themselves will be archived persistently in the FMA Event Registry, and a copy can be found here: http://fma.eng/documents/engineering/portfolios/2005/019.zfs/ -- Mike Shapiro, Solaris Kernel Development. blogs.sun.com/mws/ From sacadmin Wed Mar 1 01:09:54 2006 Received: from nis-uk.uk.sun.com (nis-uk.UK.Sun.COM [129.156.85.41]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id k2199rIQ007158 for ; Wed, 1 Mar 2006 01:09:54 -0800 (PST) Received: from enospc.uk.sun.com (enospc [129.156.173.14]) by nis-uk.uk.sun.com (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k2199qoR007398; Wed, 1 Mar 2006 09:09:52 GMT Received: from [129.150.120.102] (vpn-129-150-120-102.UK.Sun.COM [129.150.120.102]) by enospc.uk.sun.com (8.13.4+Sun/8.13.3/CTE 3.0) with ESMTP id k2199qRu027761; Wed, 1 Mar 2006 09:09:52 GMT Message-ID: <44056462.7020106@Sun.COM> Date: Wed, 01 Mar 2006 09:07:46 +0000 From: Darren J Moffat User-Agent: Thunderbird 1.5 (X11/20060113) MIME-Version: 1.0 To: Michael Shapiro CC: psarc@sac.eng.sun.com, eric.schrock@Sun.COM Subject: Re: PSARC 2006/139 FMA for ZFS References: <200603010044.k210i4pF184108@poptart.sfbay.sun.com> In-Reply-To: <200603010044.k210i4pF184108@poptart.sfbay.sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Status: RO Content-Length: 727 Michael Shapiro wrote: > This case introduces a set of ZFS FMA events that are produced when ZFS > detects device errors, and a corresponding fmd(1M) plug-in to process these > events. An FMA portfolio has been submitted and reviewed for this feature. > > This case seeks binding for a Micro release (ZFS is being backported to a > Solaris 10 Update). As the case defines new FMA events and straightforwardly Nit picking: That would be patch binding you want. There is a very subtle difference between micro and patch. Patch binding means that the changes are removable since patches need to be able to be backed out. I don't see anything in this cases that wouldn't make it suitable to be patch. -- Darren J Moffat