From owner-freebsd-questions@freebsd.org Wed Nov 21 21:43:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F3D0114768A for ; Wed, 21 Nov 2018 21:43:59 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [IPv6:2a01:4f8:191:217b::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mail.bsd4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63C00782B7 for ; Wed, 21 Nov 2018 21:43:57 +0000 (UTC) (envelope-from herbert@gojira.at) Date: Wed, 21 Nov 2018 22:43:48 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail201809; t=1542836629; bh=HpabXocJ3BcRc7EANJISUuKx2/NBn9gCzOfrXkarFMI=; h=Date:Message-ID:From:To:Subject:MIME-Version:Content-Type:from:to: subject:date:content-type:mime-version:message-id; b=DPysQENCtG6XFjVQEh9dvNBVdVZd2yfS/8ZJve1r9y8f22vx85ZDlVTPYWxPeFGI1 OSnqEudAAPXOSUo5SLldcYzbhcibQeCb6gUt9Q5GOcUkbwHUZMYh96QizFgr02pr7G nVRmsQX25CyB0SpxRdv6ep+tc9WSrwpjXOgqDMcZtYQS/XElHjaYB1x5YvFNw2YKe/ t7ntSapl/8js7QhFUzDe8kJ8ZhYvqeWou3mDqHE9oE2ZknReZPXUZGxDAUX3zGV/AA r9zVnfuzWuLIePPBZnN6V3+1AefaMAK+sC6gdPVN7zx90jGDdgV/PkgGpqiCtoecQD ZaEDhQVfs8Htg== Message-ID: <87y39mqf6z.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: freebsd-questions@freebsd.org Subject: Re: ZFS pool - HEALTH fault In-Reply-To: References: <4f40f0c404b8384a571f0c13eb9c2136.squirrel@webmail.harte-lyne.ca> <20181121174530.GA3992@neutralgood.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/27.0 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 63C00782B7 X-Spamd-Result: default: False [-3.76 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gojira.at]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:191:217b::25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[gojira.at]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; DKIM_TRACE(0.00)[gojira.at:+]; MX_GOOD(-0.01)[mail.bsd4all.net]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-1.27)[ipnet: 2a01:4f8::/29(-3.43), asn: 24940(-2.91), country: DE(-0.01)]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2018 21:43:59 -0000 On Wed, 21 Nov 2018 22:28:57 +0100, "James B. Byrne via freebsd-questions" wrote: > > On Wed, November 21, 2018 12:45, Kevin P. Neal wrote: > > On Wed, Nov 21, 2018 at 09:33:32AM -0500, James B. Byrne via > > freebsd-questions wrote: > >> Immediately following an upgrade from FreeBSD-11.1 to 11.2p4 we > >> received the following warning. I can see the suggested remedy > >> but I need to know why this has happened first. We have > >> previously upgraded numerous hosts from FreeBSd-11.1 to 11.2, > >> all of which are using zfs, and no other system has reported > >> such a fault, > >> > >> ZFS pool - HEALTH fault > > > > This message that says "HEALTH fault" comes from what? What command > > prints this message? > > It comes from a regularly scheduled health check script whose relevant > portion is: > > condition=$(/sbin/zpool status | egrep -i > '(DEGRADED|FAULTED|OFFLINE|UNAVAIL|REMOVED|FAIL|DESTROYED|corrupt|cannot|unrecover)') > if [ "${condition}" ]; then > emailSubject="`hostname` - ZFS pool - HEALTH fault" > problems=1 > fi > > Given that the status is none of the above I infer that one or more of > the words |corrupt|cannot|unrecover| appeared in whatever message > zpool status emitted. However, running this command from the command > line produces nothing containing any of the trigger words. UNAVAIL in "still be used, but some features are unavailable". -- Herbert