Date: Mon, 18 Nov 2024 17:31:30 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282832] makefs zfs creates images with the same guid Message-ID: <bug-282832-227-6FY9GJbytH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282832-227@https.bugs.freebsd.org/bugzilla/> References: <bug-282832-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282832 --- Comment #7 from Pat Maddox <pat@patmaddox.com> --- I'll have to think about this some more... because I wonder if zfs-reguid should accept a fixed value? Consider this: a build script that creates a root pool, a read-only data po= ol, and a writeable data pool. I would want the build script to just produce a single image each. Then when attaching them to VMs, I would want them to ha= ve a different GUID per VM - but also retain their GUIDs within a single VM. So it would look like: for vm in vm1 vm2 vm3; do cp root.zfs ${vm}.root.zfs import_pool ${vm}.root.zfs zfs reguid ${vm}-root $(lookup_guid vm1 root) export_pool ${vm}-root cp data.zfs ${vm}.data.zfs import_pool ${vm}.data.zfs zfs reguid ${vm}-data $(lookup_guid vm1 data) export_pool ${vm}-data done --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282832-227-6FY9GJbytH>