From owner-freebsd-current@freebsd.org  Sun Aug 30 06:48:37 2020
Return-Path: <owner-freebsd-current@freebsd.org>
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 03E4E3CDD2D
 for <freebsd-current@mailman.nyi.freebsd.org>;
 Sun, 30 Aug 2020 06:48:37 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 ESMTPS id 4BfP785xlkz4g59;
 Sun, 30 Aug 2020 06:48:36 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from pi by home.opsec.eu with local (Exim 4.92.3 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1kCH8k-000Pbv-Bo; Sun, 30 Aug 2020 08:48:34 +0200
Date: Sun, 30 Aug 2020 08:48:34 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: Matthew Macy <mmacy@freebsd.org>
Cc: freebsd-current <freebsd-current@freebsd.org>
Subject: Re: OpenZFS support merged
Message-ID: <20200830064834.GU3539@home.opsec.eu>
References: <CAPrugNrgNUpaG3Wd=3crdsKV4iA83w+32hyzYbW0j_omOTo+wA@mail.gmail.com>
 <20200829154727.GS3539@home.opsec.eu>
 <CAPrugNrGqBgqvequawRt=wQ_=TFT5S47J6UKK32Fw7rLmdN6cg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPrugNrGqBgqvequawRt=wQ_=TFT5S47J6UKK32Fw7rLmdN6cg@mail.gmail.com>
X-Rspamd-Queue-Id: 4BfP785xlkz4g59
X-Spamd-Bar: ----
X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[];
 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.33
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Aug 2020 06:48:37 -0000

Hi!

> > > I caution against 'zpool upgrade' for the next few weeks.
> > > https://svnweb.freebsd.org/base?view=revision&revision=364746

> > A system running r363767 can upgrade to some revision after r364746
> > and reboot and come up without big issues, running the new openzfs code ?
> > Or is some additional step required ?

> Barring some unusual configuration that no one else there should not be a
> problem. The only known issue of immediate concern (that was only raised a
> day or two ago :-/) is zfs delegation in poudriere.

This is my package builder box, where I also receive mail, so ... 8-}

> If you rely on that I'd say wait a couple days, otherwise proceed.

It has it's files on a ZPOOL.

How can I find if my poudriere uses zfs delegation ?

https://www.freebsd.org/doc/handbook/zfs-zfs-allow.html

says something about:

sysctl vfs.usermount

which returns 0 (so no usermounts) and:

zfs allow -l zroot/pou

which returns empty. So I guess I can upgrade.

-- 
pi@opsec.eu            +49 171 3101372                    Now what ?