From nobody Tue Sep 28 16:23:28 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7A0A417E2AD8 for ; Tue, 28 Sep 2021 16:23:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJlDx31SZz3rJc; Tue, 28 Sep 2021 16:23:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f177.google.com with SMTP id n64so11298466oih.2; Tue, 28 Sep 2021 09:23:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q28fKIXUCz+xxA/4OpsflrnQCMUjCB6Szp9ePyHL61U=; b=eCr01voUkRDrhVqxyOjNB9uUAkNuVP+9MTgLZY5m1ZVepbZzqu2LxceWifRSkNWPRm tgY0AKzl0nETdNfi+uxcP8uyQqbUEQ7WGF6GNhAcHlzsJlYVvG/s6YQnlQNFy/hRu8zK p2QzaN81xOJN+jaTKuL/+ukGh4Ej4nwKwsNSTSyc0UOvPBcauzCb+jgzJxfPs2CQJ7ex NzEsnbyih+Tk29bXnrkh2zfFqY5lLT7WCnyErdQxM5pxUabf5/D4IaR6OpkAXVfu4TEC rgHNSPGn0F7hMSd+Nil+LFCSuEtXvHcoSUE80lL6Vu/6VFE2TG8j3x/HlFhQ2GC9yyQ1 cIEg== X-Gm-Message-State: AOAM532ewfYMVVlPuuRThJxTdfuI/IuL5jJeD6mUuk+oaFf7Q8CW+9j4 IA4w7FLPJcBNVJNsRyDYR71ltxGQ5bSzHFo/a+V9Civt X-Google-Smtp-Source: ABdhPJww581kvglamxRQbTsc0I9MEoCOE60PTNy2BmXHZn48H91KB3LDTTzV1VWTG7JXkhgDeiGyt6vg+YPvA70K6r4= X-Received: by 2002:a54:4e94:: with SMTP id c20mr4249737oiy.57.1632846219307; Tue, 28 Sep 2021 09:23:39 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> In-Reply-To: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> From: Alan Somers Date: Tue, 28 Sep 2021 10:23:28 -0600 Message-ID: Subject: Re: Building ZFS disk images To: "Rodney W. Grimes" Cc: Mark Johnston , David Chisnall , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HJlDx31SZz3rJc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Sep 28, 2021 at 10:15 AM Rodney W. Grimes wrote: > > > On Tue, Sep 28, 2021 at 9:48 AM Rodney W. Grimes > > wrote: > > > > > > > On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote: > > > > > > > > > > On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote: > > > > > > There's this: > > > > > > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I > > > > > > haven't used it myself. > > > > > > > > > > Would it be useful to have an rc.d script that can run this, probably > > > > > just on the root pool? It could be configured to run only upon the > > > > > first boot, like growfs already does. > > > > > > > > Absolutely! > > > > > > Ewwwwwwwwww! :-) > > > > > > > > > > > > > > On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote: > > > > > > > > > > > > > On 05/08/2021 13:53, Alan Somers wrote: > > > > > > > > I don't know of any way to do it using the official release scripts > > > > > > > > either. One problem is that every ZFS pool and file system is supposed > > > > > > > > to have a unique GUID. So any kind of ZFS release builder would need to > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > > > > re-guid the pool on first boot. > > > > > > Isnt the proper place to solve this lack of Unique UUID creation > > > in the tool(s) that are creating the zfs pool in the first place. > > > > > > Fixing it "post boot" seems to be a far to late hack and doesnt > > > fix any of the situations where one might import these pools > > > between creation and first boot. > > > > No, because you might create a VM image once, then instantiate it > > dozens or thousands of times. The firstboot solution is great because > > it lets you reuse the same image file. > > I would continue to argue that the place to fix this is in the > "instantiate tool". ESXI vmfs deals with this all the time > when you clone a disk. And again the "fix at boot" does not > deal with the problem in that if I "instatiate" 10 copies of > a zpool for VM's and then try to mount 2 of them at once on > the host this problem rares it head. Fix the problem as close > to point of creation as possible for minimal issues in all > operations for everyone. But that requires ESXI, or whatever VM system you're using, to know about ZFS and GPT, and to know to look for a zpool on the 3rd partition, right? That seems like a lot to ask, especially since the logic would have to be duplicated for ESXI, vm-bhyve, OpenNebula, etc etc. > > > > > > > > > > > > > > > > > > > > Is there a tool / command to do this? I've hit this problem in the > > > > > > > past: I have multiple FreeBSD VMs that are all created from the same > > > > > > > template and if one dies I can't import its zpool into another because > > > > > > > they have the same UUID. > > > > > > > > > > > > > > It doesn't matter for modern deployments where the VM is stateless and > > > > > > > reimaged periodically but it's annoying for classic deployments where I > > > > > > > have things I care about on the VM. > > > > > > > > > > > > > > David > > > > > > > > > > > > > > -- > > > Rod Grimes rgrimes@freebsd.org > > > > -- > Rod Grimes rgrimes@freebsd.org