From owner-freebsd-current@freebsd.org Thu Jul 30 15:33:46 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 AEAB53A8624 for ; Thu, 30 Jul 2020 15:33:46 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BHZFQ4F70z4W5q for ; Thu, 30 Jul 2020 15:33:46 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 6B8BD1FA33 for ; Thu, 30 Jul 2020 15:33:46 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-lj1-f174.google.com with SMTP id t23so5829322ljc.3 for ; Thu, 30 Jul 2020 08:33:46 -0700 (PDT) X-Gm-Message-State: AOAM530ZPAP7/kcLqfJTVP4+I2ZqITj1Z++MgMxUdRv0NnixRMQWd48Q DKbjkG/N0VdIsu0mqCrW2J+bRFcNqpC7FkcqGPc= X-Google-Smtp-Source: ABdhPJx2J4CfhwOBcLXGJTKKsT1LwB9HkNtqDAoXBBee0u9NfZh7fqRFx3E+FRhVQaF+XuLlgTeg06n0L5PsgzcALj4= X-Received: by 2002:a2e:b00c:: with SMTP id y12mr1857981ljk.18.1596123224743; Thu, 30 Jul 2020 08:33:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Macy Date: Thu, 30 Jul 2020 08:33:33 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CFT for vendor openzfs - week 4 reminder + memdisk images To: bsd-lists@bsdforge.com Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.33 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: Thu, 30 Jul 2020 15:33:46 -0000 On Wed, Jul 29, 2020 at 20:16 Chris wrote: > On Tue, 28 Jul 2020 21:16:28 -0700 Matthew Macy mmacy@freebsd.org said > > > On Tue, Jul 28, 2020 at 21:06 Chris wrote: > > > > > On Tue, 28 Jul 2020 20:50:33 -0700 Matthew Macy mmacy@freebsd.org sai= d > > > > > > > On Tue, Jul 28, 2020 at 20:43 Chris wrote: > > > > > > > > > On Tue, 28 Jul 2020 20:08:33 -0700 Matthew Macy mmacy@freebsd.org > said > > > > > > > > > > > On Tue, Jul 28, 2020 at 8:03 PM Chris > > > wrote: > > > > > > > > > > > > > > On Tue, 28 Jul 2020 19:10:21 -0700 Matthew Macy > mmacy@freebsd.org > > > said > > > > > > > > > > > > > > > On Wednesday, July 8th I issued the initial call for testin= g > for > > > the > > > > > > > > update to HEAD to vendored openzfs. We'd like to give users > > > roughly a > > > > > > > > month to test before merging. The tentative merge date is > August > > > > > > > > 17th. > > > > > > > > > > > > > > > > Again, I hope it's not terribly controversial to point out > that > > > > > > > > it really rests with users of non amd64 platforms to test t= o > > > avoid > > > > > any > > > > > > > > unpleasant surprises the next time they update their trees > > > following > > > > > > > > the merge. > > > > > > > > > > > > > > > > amd64, i386, and aarch64 memdisk images can be found at: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://people.freebsd.org/~freqlabs/freebsd-openzfs-3d833bea-f10f94aa-20= 20072900/ > > > > > > > > > > > > > > Is this in an attempt to replace the opensolaris version used > now? > > > > > > > > > > > > The word "attempt" is a misnomer. If you search the mail archiv= es > > > this > > > > > > has been the PoR for some time. > > > > > Sure. OK. I caught this thread. But must have missed the > announcement > > > > > of the intent to replace the opensolaris version with openzfs. > > > > > Do you recall which mailing list that was made to? > > > > > > > > > > Thank you for your quick reply, Matthew. > > > > > > > > > > > > > Apart from the 3 previous CFT mails, the initial intent was > discussed in > > > > December 2018. Getting FreeBSD support integrated in to openzfs too= k > a > > > lot > > > > more incremental PRs than I anticipated. > > > > > > > > > > > > > > > https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072422.= html > > > > > > Thank you very much, Mathew. Sorry for any bother. > > > > > > > > > No bother or not much at least. It=E2=80=99s just been a long haul and = I=E2=80=99d like > > to > > wrap this up. > No doubt. > FTR I'm not looking to impede you. :-) > My only concern would be that I'd need to remaster the art of ZFS. I've > got 1500 installs to maintain, and any changes tend to alarm me. :-) > I see we're a bit behind the others, if this status report is current: > > https://docs.google.com/spreadsheets/d/1CFapSYxA5QRFYy5k6ge3FutU7zbAWbaeG= N2nKVXgxCI/edit#gid=3D0 > Will your impending commit move us closer? Is there anything others > like myself can do to help? Close to 90% of the sources files in openzfs are shared between Linux and FreeBSD. So the features will, give or take a line item, be the same. For non developers the main thing they can do to help out is to run it in their own environments to identify any changes in behavior or regressions. If you=E2=80=99re doing 1500 installs it=E2=80=99s in your best interest to ma= ke this as smooth a transition as possible. However, it=E2=80=99s not something you=E2= =80=99re going to face until you move to 13. The openzfs port is available to those who want to run it on 12. -M > > > Thanks again, Matthew. > > --Chris > > > > -M > > > > > > > >