Date: Thu, 5 Aug 2021 15:29:32 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Alan Somers <asomers@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Building ZFS disk images Message-ID: <8ab3d440-889e-25d4-71f9-e7ae2386daeb@FreeBSD.org> In-Reply-To: <CAOtMX2hxj%2Bxehjk-5QoF4ao4z3Fs7ifxTjzRsQrXz7Z8g16eVw@mail.gmail.com> References: <16473d5f-1727-233a-7a95-a21c5b48b9ce@FreeBSD.org> <CAOtMX2hxj%2Bxehjk-5QoF4ao4z3Fs7ifxTjzRsQrXz7Z8g16eVw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8ab3d440-889e-25d4-71f9-e7ae2386daeb>