From owner-freebsd-current@freebsd.org Mon Jul 13 23:39:33 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 9E9933752D2 for ; Mon, 13 Jul 2020 23:39:33 +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 4B5Kqn3ZKxz3S7C for ; Mon, 13 Jul 2020 23:39:33 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (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 55EBE12049 for ; Mon, 13 Jul 2020 23:39:33 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-lj1-f170.google.com with SMTP id s9so20217928ljm.11 for ; Mon, 13 Jul 2020 16:39:33 -0700 (PDT) X-Gm-Message-State: AOAM532IlUccSOOMZbLXvOrIGiX3uunVIfDqc0dH4qEXNK/HKg+gK2B3 saJkSuEETFX9NvE6NYciW38ZPXgASbM6z366hqI= X-Google-Smtp-Source: ABdhPJynqYRRz7BK/MxpvZCYvAEHZHySPaq94Ww3aX+/ESbxUpaAS7oZ9ypIWq8MN1Vm4xxQBTPRoDWVvBuDjM9v8gY= X-Received: by 2002:a2e:943:: with SMTP id 64mr861677ljj.445.1594683571818; Mon, 13 Jul 2020 16:39:31 -0700 (PDT) MIME-Version: 1.0 References: <772a8068-cf16-4fb8-8cb9-5592b6d92490@yggdrasil.evilham.com> In-Reply-To: <772a8068-cf16-4fb8-8cb9-5592b6d92490@yggdrasil.evilham.com> From: Matthew Macy Date: Mon, 13 Jul 2020 16:39:20 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CFT for vendor openzfs - week 2 reminder To: Evilham Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" 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 23:39:33 -0000 To help us keep track, please file an issue https://github.com/zfsonfreebsd/zof/issues Thanks. On Mon, Jul 13, 2020 at 3:39 PM Evilham wrote: > > 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