From owner-freebsd-stable@freebsd.org Fri Apr 17 21:40:26 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4A5342ABFE5; Fri, 17 Apr 2020 21:40:26 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493qJT1Lbjz3KF0; Fri, 17 Apr 2020 21:40:25 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (65-100-43-2.dia.static.qwest.net [65.100.43.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "chombo.houseloki.net", Issuer "brtsvcs.net CA" (verified OK)) by echo.brtsvcs.net (Postfix) with ESMTPS id AA49638D28; Fri, 17 Apr 2020 21:40:23 +0000 (UTC) Received: from [IPv6:2602:41:642b:630:6c16:8993:6207:3a64] (unknown [IPv6:2602:41:642b:630:6c16:8993:6207:3a64]) by chombo.houseloki.net (Postfix) with ESMTPSA id 2AF9017F4; Fri, 17 Apr 2020 14:40:23 -0700 (PDT) Subject: Re: OpenZFS port updated To: Kyle Evans Cc: FreeBSD Current , FreeBSD-STABLE Mailing List , Ryan Moeller References: From: Mel Pilgrim Message-ID: <8abb14b2-7426-559d-af7e-c339fa130515@bluerosetech.com> Date: Fri, 17 Apr 2020 14:40:23 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493qJT1Lbjz3KF0 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of list_freebsd@bluerosetech.com designates 2607:f740:c::4ae as permitted sender) smtp.mailfrom=list_freebsd@bluerosetech.com X-Spamd-Result: default: False [-5.65 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx:relay3.brtsvcs.net]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bluerosetech.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-3.35)[ip: (-8.66), ipnet: 2607:f740:c::/48(-4.25), asn: 36236(-3.81), country: US(-0.05)]; TO_DN_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:f740:c::/48, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:40:26 -0000 On 2020-04-17 13:31, Kyle Evans wrote: > On Fri, Apr 17, 2020 at 3:14 PM Mel Pilgrim > wrote: >> >> On 2020-04-17 11:35, Ryan Moeller wrote: >>> The FreeBSD platform support in OpenZFS does not yet include all >>> features present in FreeBSD’s ZFS. Some notable changes/missing >>> features include: >> [...] >>> * pre-mountroot zpool.cache loading (for automatic pool imports) >>> >>> To the last point, this mainly effects the case where / is on ZFS and >>> /boot is not or is on a different pool. OpenZFS cannot handle this >>> case yet, but work is in progress to cover that use case. Booting >>> directly from ZFS does work. >> >> To be clear, this means OpenZFS currently does not support / on >> GELI-encrypted disks, correct? > > If you have a legacy setup with a bootpool, that is correct. Since > 12.0+ the bootpool is almost completely redundant except for some odd > setup that I can never remember. For legacy setups, the bootpool > can/should be merged into your root pool if it's feasible. Yes, these are the "legacy" configuration with a small, unecrypted pool containing /boot and the keys to attach the encrypted root pool. Could the case you're thinking of be avoiding manual entry of a password at boot?