From owner-freebsd-stable@freebsd.org Mon Jul 31 06:59:38 2017 Return-Path: Delivered-To: freebsd-stable@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 99A7CDCB70B for ; Mon, 31 Jul 2017 06:59:38 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 430B06A92A for ; Mon, 31 Jul 2017 06:59:38 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.239] (probe.42.lan [172.29.1.239]) by limbo.b1t.name (Postfix) with ESMTPSA id 3A99BDE for ; Mon, 31 Jul 2017 09:51:12 +0300 (EEST) To: FreeBSD Stable From: Volodymyr Kostyrko Subject: ZFS bootable pool detection code strictness Message-ID: <99c0d5c2-6581-4516-6938-50ad84670f2e@b1t.name> Date: Mon, 31 Jul 2017 09:51:11 +0300 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=b1t.name; s=dkim; t=1501483873; bh=kCpO6ngEY0F8PYndcmGQXXmpxrEmiEuiNQE+49Fp67A=; h=To:From:Subject:Message-ID:Date:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1l3oIAV9JSe/lH1ubQJ5aeECJmIu+Fc5zwfWAYJm/BVpV2thv1vDGj9SFRmhDT1at0HctwHD4jbMhlVA3d0ickUQebobVdIyDgN0zRXx9oW2WJFRY3DSgyK1IDtE7zPFxxwcYP7mh9Bur8+NO8kIHGXsnoOvTa6BGVp3pLAFfWQ= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jul 2017 06:59:38 -0000 Hi all. First of all thank you for working on ZFS support. ZFS stability is unmatchable and I'm heavily relying on ZFS right now. Last bootcode updates had given me some fun time. My pool contains some vdevs with skein enabled so new bootcode forced my pool out of boot. I know that my hands are dirty but I'm sure the pool is bootable as everything required for booting was never touched by unsupported options (I know the boot will fail instantly). Yes, I do like experimenting a lot. From my point of view the code committed is just too strict locking out anyone who tries to play with extra pool properties. The analyzer itself is nice and I don't want it to go away as every extra bit of information about why boot may fail is precious but I'd be very happy to have some loader knob to disable the pool blacklisting so that the code will test the pool, will report everything it finds unsuitable but would allow a booting attempt. Thanks in advance. -- Sphinx of black quartz judge my vow.