From owner-freebsd-current@freebsd.org Thu Aug 30 05:42:00 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 813D710951A2 for ; Thu, 30 Aug 2018 05:42:00 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [140.82.23.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "mail.nomadlogic.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E69ED72B03; Thu, 30 Aug 2018 05:41:59 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.203] (cpe-76-175-75-27.socal.res.rr.com [76.175.75.27]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id afd48403 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 29 Aug 2018 13:41:58 -0700 (PDT) Subject: Re: beadm vs bectl To: Allan Jude , freebsd-current@freebsd.org References: <1c247846-cdd1-fa49-9033-95b7ff660a60@nomadlogic.org> <25b137fa-5b09-fa0b-e261-91d1a3fd06f3@freebsd.org> From: Pete Wright Message-ID: <70ce5c87-0271-d31d-fe65-4545f74ae1d3@nomadlogic.org> Date: Wed, 29 Aug 2018 13:41:57 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <25b137fa-5b09-fa0b-e261-91d1a3fd06f3@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Thu, 30 Aug 2018 05:42:00 -0000 On 8/27/18 3:22 PM, Allan Jude wrote: > On 2018-08-27 14:50, Pete Wright wrote: >> hi there - i have a zfs based system where /boot is on its own pool. >> beadm seems happy enough with this setup but bectl errors out like so: >> >> $ sudo bectl list >> / and /boot not on same device, quitting >> $ >> >> $ beadm list >> BE                 Active Mountpoint  Space Created >> default            NR     /           47.6G 2018-03-02 20:30 >> snapshot_02262018  -      -            1.5G 2018-03-03 14:38 >> badresume_05122018 -      -            4.4G 2018-05-12 19:45 >> 11_2_beta          -      -            2.6G 2018-05-13 18:26 >> resume_works       -      -           12.6G 2018-06-01 16:45 >> $ >> >> reading the manpage for bectl it doesn't mention this being an issue. >> so i guess i have two questions: >> 1) is it a bad thing(tm) to have /boot on its own pool? >> 2) assuming that having /boot on its  own pool, why does bectl not work >> with this configuration? >> >> thanks! >> -pete >> > Your /boot being on a separate pool can never work, since you can't take > a consistent snapshot of / and have it include your kernel (which is > under /boot/kernel which is a separate pool) > > Do you know why you have 2 separate pools? If it was for GELI support, > FreeBSD 12.0 will not require two separate pools anymore, and there will > be migration instructions shortly. > thanks Allan!  that is precisely why i have a separate /boot IIRC - i use GELI to encrypt zroot.  i'll keep my eyes open for migration instructions which i'll be sure to test out and provide feedback on. thanks! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA