From owner-freebsd-fs@freebsd.org Tue Feb 16 17:59:11 2021 Return-Path: Delivered-To: freebsd-fs@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 04ABB541B59 for ; Tue, 16 Feb 2021 17:59:11 +0000 (UTC) (envelope-from lopez.on.the.lists@yellowspace.net) Received: from mail.yellowspace.net (mail.yellowspace.net [62.146.62.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with UTF8SMTPS id 4Dg7yQ0XZwz4pj0 for ; Tue, 16 Feb 2021 17:59:09 +0000 (UTC) (envelope-from lopez.on.the.lists@yellowspace.net) Subject: Re: Migrating from base to OpenZFS: GELI drives, send/receive, and sysctls/loader.conf To: freebsd-fs@freebsd.org References: <183ed751-5a2e-5468-c82c-670820bac138@yellowspace.net> From: Lorenzo Perone Message-ID: <3b13d100-92af-276c-dd58-3d914eeea432@yellowspace.net> Date: Tue, 16 Feb 2021 18:59:01 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Dg7yQ0XZwz4pj0 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lopez.on.the.lists@yellowspace.net designates 62.146.62.106 as permitted sender) smtp.mailfrom=lopez.on.the.lists@yellowspace.net X-Spamd-Result: default: False [-3.18 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[62.146.62.106:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.yellowspace.net]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[yellowspace.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[62.146.62.106:from:127.0.2.255]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.88)[-0.882]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15598, ipnet:62.146.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Feb 2021 17:59:11 -0000 Am 15.02.21 um 21:08 schrieb Freddie Cash: > On Mon., Feb. 15, 2021, 9:37 a.m. Lorenzo Perone, > > wrote: > > Hi All, > > I have followed regularly the development of openzfs for FreeBSD and I > guess I'm ready and eager to give it a first try on a 12.2 updated > system by using the port. > > Particularly watching the (now a little outdated, but still good) talk > by Alan Jude @ EuroBSDCon 2019 was very encouraging. > > What I'm planning as a first run is: > > On the same machine: > > - Boot with openzfs_load instead of zfs_load > - Import the "base" created pool with openzfs > - Create a new pool with openzfs > - Send/Receive and/or rsync data from the old to the new one > > > A few questions arised for which I didn't find an answer yet in the > official documentation. > > 1) Will a pool on GELI drives import well with openzfs too? I'd assume > yes, why shouldn't it. Just asking to correct me if there are any > precautions I should be taking or surprises to expect. > > 2) Will the "old" settings be honored by openzfs, such as > vfs.zfs.arc_min, vfs.zfs.arc_max in /boot/loader.conf? > > 3) Is there an openzfs_enable as opposed to zfs_enable in rc.conf (to > import/mount pools at boot)? Or is zfs_enable just compatible? > > 4) As far as I know, it should be possible to send/receive data from an > unencrypted dataset to an encrypted one. Is this advisable from an "old > base" zfs dataset (not encrypted, on geli) to a new openzfs one > (encrypted at the dataset level), or should we resort to rsync? > > 5) What's the actual current status on extended attributes? Will they be > retained in a send/receive from FreeBSD-"old" to FreeBSD-OpenZFS? I have > a few shares on that machine where macs have "dropped" their EAs via > AFP/SMB, what should I expect? > > Thanks a lot for any attention by people who know this right away, > > > If this is a boot pool, create a new boot environment and reboot into it > before making any changes. In the new BE, install the port, update > loader.conf and test things out. So long as you don't do a "zpool > upgrade" or enable any new features, then you can always change BE at > the loader menu to revert back to the working config. No, for boot SSDs I usually resort to UFS on gmirror + gjournal... ZFS on root is appealing (boot environments and rollbacks..) but until now booting has been something I have rather kept out of ZFS, legacy or not. Maybe one day.. :) > Doing it that way saved me a lot of headaches when trying to use the > openzfs packages (which don't work on 12.2). Had to eventually install > via the ports tree. Good to know. I'd expect something like this to be fixed soon, however? > A bunch of sysctls are the same, a bunch are named slightly differently, > and there's a whole bunch of new ones. Best bet is to comment then all > out and see if the autotune setup works for you. If not, then tweak the > new sysctls as you go. I'm usually totally fine with autotune, with the only exception of vfs.zfs.arc_min and vfs.zfs.arc_max... I'll dump them out once it starts working. > It's just zfs_enable in rc.conf for both base and port ZFS. Cool. > You can "zfs send" between versions without issue. Double cool :) > Can't help with the GELI or xattrs questions as I don't use those. I guess GELI is a no-brainer, xattrs I guess I'll find out.. Best Regards and thanx a lot!! Lorenzo