From nobody Tue Sep 28 17:46:07 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 03C4817EAD42 for ; Tue, 28 Sep 2021 17:46:16 +0000 (UTC) (envelope-from me+freebsd@igalic.co) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (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 "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJn475xKcz4VxP; Tue, 28 Sep 2021 17:46:15 +0000 (UTC) (envelope-from me+freebsd@igalic.co) Date: Tue, 28 Sep 2021 17:46:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=igalic.co; s=protonmail; t=1632851167; bh=/QNh6cQLetrvqZ95vmKXWdEubDY1s9SWwXQ+g4Haids=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=PBDhi5xQqgeNCMlas8N+TXihEirjdshNWBoQQmrwfSzGaSWlUszo8vsrY5kinBtgK QvlRU17NhFHD22o0c/NnHryJ76NW1z9rG22EvfhwOj6hzpQmprD2GM3NlQpLCl7+C/ Q/KXWoUEojnnnQ+44LzDhd17syjgrXlKUUdwwwzRept/bGlsJmVZAxTOJEWIvXssS0 /TsxXRROvmofJCyOKriOyWGTv5Ps9EwuYjp6xvS8/MPMBR1EuustbUDN1gP2oyKDup Ev9h5biGTCXt+sn+nCG37HnVQexQcN5X8qjpCT2uLbK0vHI+z8Sp0SVv8H0as80Mvn 0lzBYfPxJ2ang== To: "Rodney W. Grimes" From: =?utf-8?Q?Mina_Gali=C4=87?= Cc: Alan Somers , Mark Johnston , David Chisnall , freebsd-current Reply-To: =?utf-8?Q?Mina_Gali=C4=87?= Subject: Re: Building ZFS disk images Message-ID: In-Reply-To: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> References: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> 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 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch X-Rspamd-Queue-Id: 4HJn475xKcz4VxP X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[freebsd] X-ThisMailContainsUnwantedMimeParts: N =E2=80=90=E2=80=90snip--- *puts on cloud-init contributor hat* > > 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. a lot of folks use cloud-init for provisioning different Unices onto different virtualisation (cloud) platforms. We could fix it there. We already extend paritions, filesystems and ZFS pools in cloud-init. now, again, one could argue that's the wrong place to do any of that, and we should just be using firstboot. But the problem seems to be that a lot folks out there got into the habit of creating and publishing (FreeBSD) images, seem to have forgotten or never knew about firstboot, and don't to set it. Mina Gali=C4=87 Web: https://igalic.co/ PkgBase: https://alpha.pkgbase.live/