From owner-freebsd-fs@freebsd.org Fri Apr 21 09:39:43 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51DB1D475DD for ; Fri, 21 Apr 2017 09:39:43 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A57E017E2 for ; Fri, 21 Apr 2017 09:39:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA29796; Fri, 21 Apr 2017 12:39:40 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1d1V2S-000Nf9-A2; Fri, 21 Apr 2017 12:39:40 +0300 Subject: Re: vdev state changed & zfs scrub To: Martin Simmons , Dan Langille Cc: freebsd-fs@FreeBSD.org References: <0030E8CC-66B2-4EBF-A63B-91CF8370D526@langille.org> <597c74ea-c414-cf2f-d98c-24bb231009ea@gmail.com> <106e81a2-4631-642d-6567-319d20d943d2@FreeBSD.org> <201704201514.v3KFE4P8001833@higson.cam.lispworks.com> From: Andriy Gapon Message-ID: <43bac6ef-b588-5eb1-08cb-25caee8ace9b@FreeBSD.org> Date: Fri, 21 Apr 2017 12:38:43 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <201704201514.v3KFE4P8001833@higson.cam.lispworks.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 09:39:43 -0000 On 20/04/2017 18:14, Martin Simmons wrote: > No, I think he meant change kern.notice to something else such as kern.info so > you don't see them in /var/log/messages (as controlled by /etc/syslog.conf). Yes, that's exactly what I meant. Sorry for not being clear. -- Andriy Gapon