From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 18:07:16 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 700941065673 for ; Tue, 9 Aug 2011 18:07:16 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 302758FC17 for ; Tue, 9 Aug 2011 18:07:15 +0000 (UTC) Received: by vws18 with SMTP id 18so295688vws.13 for ; Tue, 09 Aug 2011 11:07:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.20.232 with SMTP id q8mr7568865vde.125.1312913235184; Tue, 09 Aug 2011 11:07:15 -0700 (PDT) Received: by 10.220.85.129 with HTTP; Tue, 9 Aug 2011 11:07:15 -0700 (PDT) X-Originating-IP: [93.221.185.184] In-Reply-To: References: <4DF3913F.1000108@lazlarlyricon.com> <4DFB516B.30006@it4pro.pl> <4DFB6EEC.20206@lazlarlyricon.com> Date: Tue, 9 Aug 2011 20:07:15 +0200 Message-ID: From: "C. P. Ghost" To: Olivier Smedts Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: "log_sysevent: type 19 is not implemented" messages during boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 18:07:16 -0000 On Fri, Jun 17, 2011 at 5:28 PM, Olivier Smedts wrote: > 2011/6/17 Rolf Nielsen : >> 2011-06-17 16:29, Artem Belevich skrev: >> <...> >>>> >>>> Are you sure that it's harmless? It appeared for me as an evidence of >>>> pool >>>> breakage. I had these messages when I ran any zpool command on broken >>>> pool. >>>> I do't havesingle one after pool is fixed. Here's my thread on freebsd= -fs >>>> : >>>> http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011639.html >>> >>> Indeed. Same story here. Last week I've got my pool corrupted due to a >>> bad memory stick. =A0Then I've got tons of thse "log_sysevent: type >>> 19..." messages. After re-importing the pool with -F the messages went >>> away. So, from where I stand, those messages do seem to correlate with >>> a problem and should not be hushed by default. > > On mine, it pops up at boot on the console if the cache device is > inaccessible (usb key). No real problem on the pool, but an > information with more meaning would be useful. On one of my test systems, I have a zpool consisting of 3 HDDs in external enclosures attached via eSATA ports. If the enclosures are not powered (i.e. the disks are off), and the system boots, then this message appears. Of course, the zpool isn't available then, not being available physically. OTOH, when the enclosures are on, and the system boots, this message doesn't show up, and the zpool is available and healthy alright. This message appeared since ZFSv28, and on this system and in this specific scenario, it is absolutely harmless. >> /Rolf > > Olivier Smedts=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 _ -cpghost. --=20 Cordula's Web. http://www.cordula.ws/