From nobody Thu Aug 5 15:54:19 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 1829710FF395 for ; Thu, 5 Aug 2021 15:54:38 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f53.google.com (mail-ot1-f53.google.com [209.85.210.53]) (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 4GgY8G07pPz3JXN; Thu, 5 Aug 2021 15:54:38 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f53.google.com with SMTP id c2-20020a0568303482b029048bcf4c6bd9so5598451otu.8; Thu, 05 Aug 2021 08:54:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oZZNjZsDkXTvrpqUrL7S6xePeFjybib0t3QO7iju2GU=; b=pYUSysNFQ72y7pi5gFuyUkvdvbfVfVyBbQYAPo7rYVezNe9XoZvXckvpNoSxYy1HL9 6M0hG9aeh+1z/ONU0g6Gjx/B2Pco6LnXgBNtfg44GrGEnYYDKPhyFRRq84zFl6pnyJFE 1yvhhdN2kVYN9p32c0X2RQ3e7Ha2+Xou9RAwoAEx5oxBhymY1t64TI0c8d64WTxfdBc0 iYOCVOmr+3Rfu4QOJiO0owuTdg/aY3m2iUNFOpYBJhVZ+AC7ub3yN7MKRnL92QPwnI8+ JWtiKUARRntS3ezryKtYeHL0xRgfgqJ9sc4mGGNA5JKPlHy4ybsv8NMpAGHoQkPd8vkH J2tQ== X-Gm-Message-State: AOAM530huHCgXHVPRcCfvpuWX8em1RxdVQJQ1C2HJaDLhY1JRDL7yIqR Stf61IPYMTfIsgFNkNrtPe5G0XWzIQKY2md0kG/KeLIg X-Google-Smtp-Source: ABdhPJyjO98O1bODkKwgL08gBBxaEjWKn9dcvw4iA9JeemX2uI4gNQYb84dB40CruIrMeIDaNViqrqikfEKZEIDchx4= X-Received: by 2002:a9d:7e5:: with SMTP id 92mr4314579oto.18.1628178871324; Thu, 05 Aug 2021 08:54:31 -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: <16473d5f-1727-233a-7a95-a21c5b48b9ce@FreeBSD.org> <8ab3d440-889e-25d4-71f9-e7ae2386daeb@FreeBSD.org> In-Reply-To: <8ab3d440-889e-25d4-71f9-e7ae2386daeb@FreeBSD.org> From: Alan Somers Date: Thu, 5 Aug 2021 10:54:19 -0500 Message-ID: Subject: Re: Building ZFS disk images To: David Chisnall Cc: Alan Somers , freebsd-current Content-Type: multipart/alternative; boundary="00000000000041926505c8d1efca" X-Rspamd-Queue-Id: 4GgY8G07pPz3JXN X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --00000000000041926505c8d1efca Content-Type: text/plain; charset="UTF-8" There's this: https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I haven't used it myself. 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. > > 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 --00000000000041926505c8d1efca--