From owner-freebsd-current@freebsd.org Mon Jul 13 22:39:45 2020 Return-Path: Delivered-To: freebsd-current@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 9EC96373E31 for ; Mon, 13 Jul 2020 22:39:45 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [IPv6:2a02:2770::216:3eff:fee1:cf9]) (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 4B5JVl5Ggrz4cyW; Mon, 13 Jul 2020 22:39:43 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (localhost [IPv6:::1]) by yggdrasil.evilham.com (Postfix) with ESMTP id 4B5JVb281bzypJ; Tue, 14 Jul 2020 00:39:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=evilham.com; h=from:to:cc :subject:references:in-reply-to:date:message-id:mime-version :content-type; s=mail; bh=/sRE+rma83cvLMUU0k6GDDt8aSk=; b=dGokak t0VP+UC2SLEkzPT5BIW7o91DkCqEUx7njrO/NZ6TBQXg82MyEjvOi9FMxv3HcDX7 N06KfUOdWnnqCtWvbSUaKjAA/qePuEwTBVFZQVKy7/yDxTTVEG0yfg9ESsiTDVk6 7ytZRCTK7Wx9b4Jb2mS94l0l4LHVaUds9qjWs= Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 4B5JVZ5N7pzypH; Tue, 14 Jul 2020 00:39:34 +0200 (CEST) From: Evilham To: freebsd-current@freebsd.org Cc: Matthew Macy Subject: Re: CFT for vendor openzfs - week 2 reminder References: In-reply-to: Date: Tue, 14 Jul 2020 00:39:33 +0200 Message-ID: <772a8068-cf16-4fb8-8cb9-5592b6d92490@yggdrasil.evilham.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 4B5JVl5Ggrz4cyW X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=fail (headers rsa verify failed) header.d=evilham.com header.s=mail header.b=dGokak t; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 2a02:2770::216:3eff:fee1:cf9 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-3.03 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_DKIM_REJECT(0.00)[evilham.com:s=mail]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.02)[-1.017]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[evilham.com:-]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(0.00)[evilham.com,none]; NEURAL_HAM_SHORT(-0.21)[-0.213]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:196752, ipnet:2a02:2770::/32, country:NL] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Mon, 13 Jul 2020 22:39:45 -0000 On dl., jul. 13 2020, Kyle Evans wrote: > On Mon, Jul 13, 2020 at 12:27 PM Matthew Macy > wrote: >> >> On Wednesday, July 8th I issued the initial call for testing >> for the >> update to HEAD to vendored openzfs. We'd like to give users >> roughly a >> month to test before merging. The current *tentative* merge >> date is >> August 10th. I hope it's not terribly controversial to point >> out that >> it really rests with users of non amd64 platforms to test to >> avoid any >> unpleasant surprises the next time they update their trees >> following >> the merge. >> > > I've had no problems with this on a couple amd64 systems; I did > note > that my loader.conf's needed a good > s/vfs.zfs.arc_max/vfs.zfs.arc.max/ > but I'm told a compat sysctl is on the TODO list to ease the > transition. I've also been using this on amd64 for a few days without any issues, it's even fixed a bug I've been trying to figure out: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247544 I have noticed a thing though: Previously observed behaviour: 1. A new zpool is made available (e.g. geli attach) 2. The zpool is imported 3. Something happens (e.g. system reboot) and the zpool is not available anymore but also not exported 4. The zpool is made available again 5. The zpool is *still* imported 6. The zpool must be manually mounted With the patches for OpenZFS, number 5 and 6 are instead: 5. The data zpool is not imported 6. The zpool must be manually re-imported It is different behaviour, but I am very unsure about whether or not that is to be considered a bug and needs a PR. -- Evilham