From owner-freebsd-current@freebsd.org Tue Mar 20 14:29:53 2018 Return-Path: Delivered-To: freebsd-current@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 067D4F51EAC for ; Tue, 20 Mar 2018 14:29:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69D7D7551A for ; Tue, 20 Mar 2018 14:29:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id l191-v6so2882611lfe.1 for ; Tue, 20 Mar 2018 07:29:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=IoNNl3s6QCfBH3v2IgN8jozzPoajNZUgenZ/YgK5qQk=; b=c8k0OlZgQJKlCpgx26SfjmUv6aOv4gblSTLciuNBHCm/wCncqu8QgH1QSPCGwcs1wi Pfxx/LAVCtG3Gx3pamVp2lGF0wE/JZykbt3pd6oXDhXtHSqqICeh+suBGFTgy8n1D5Fu oDJW2FOi/8hwoIMtnZi+UFPxZt11OfrZVZmW1ZpWE5whHjCF7ZjLZpdpHswdifvIcppQ q5fbQVbGwqB/RwsgRyF5Pt4tIfWkzTes0UDi7zv53eGkmaVTRdGZAtCOSG0M51VDtk2h fCdgzbkr6bXo2abFevPq4VRZr8gdCgDYzOqEuZJaOZMsRpK+/aWoVrPAlU68L32QYHlV 2Tgg== X-Gm-Message-State: AElRT7F5aTZyhjkNBimN+eN2h+IT0hPWCf2Xzags85LgOnG3L3806yMQ WOa920phWkAkaJ0z2EQ/RWODiwoFRfg= X-Google-Smtp-Source: AG47ELvOMplY2rO3wshDi0Pyo74K92DEXjFEskkoYm+hP4sF+sQbQ+ajf763nGRFx4mreJYw2YNeWQ== X-Received: by 10.46.124.8 with SMTP id x8mr10552349ljc.121.1521556184913; Tue, 20 Mar 2018 07:29:44 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id l78-v6sm472818lfi.36.2018.03.20.07.29.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 07:29:44 -0700 (PDT) Subject: Re: ZFS i/o error in recent 12.0 To: =?UTF-8?Q?Trond_Endrest=c3=b8l?= , KIRIYAMA Kazuhiko Cc: freebsd-current@freebsd.org References: <201803192300.w2JN04fx007127@kx.openedu.org> From: Andriy Gapon Message-ID: <888ab314-fb1b-0e08-89d9-0447e7943b76@FreeBSD.org> Date: Tue, 20 Mar 2018 16:29:43 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 14:29:53 -0000 On 20/03/2018 09:09, Trond Endrestøl wrote: > This step has been big no-no in the past. Never leave your > bootpool/rootpool in an exported state if you intend to boot from it. > For all I know, this advice might be superstition for the present > versions of FreeBSD. Yes, it is. That does not matter at all now. > From what I can tell from the above, you never created a new > zpool.cache and copied it to its rightful place. For the _rooot_ pool zpool.cache does not matter as well. It matters only for auto-import of additional pools, if any. -- Andriy Gapon