Date: Fri, 1 Jan 2021 12:36:13 +0000 From: Rafal Lukawiecki <raf@rafal.net> To: Colin Percival <cperciva@tarsnap.com> Cc: freebsd-cloud@freebsd.org Subject: Re: 12.2 AMI Maker Issue Message-ID: <74098FC7-FEF4-4940-A405-76231A7686AF@rafal.net> In-Reply-To: <01000176bb50f67f-1b089a24-4dcc-4100-8992-d3dad12bd478-000000@email.amazonses.com> References: <01000176bb50f67f-1b089a24-4dcc-4100-8992-d3dad12bd478-000000@email.amazonses.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 1 Jan 2021, at 00:20, Colin Percival <cperciva@tarsnap.com> wrote: >=20 > Yes, that's the right solution. The disk image installed on nvd0 is *exac= tly* > the same as the release image -- it's less than 10 GB in case someone want= s to > launch onto a disk of less than 10 GB. If you're adding more packages to i= t, > wanting to expand the filesystem is not at all surprising. Thank you. Interestingly, the fs on the ARM AMI maker nvme is expanded to th= e full 10GB and do did not need the expansion. The small, ~4GB one happens t= o come only with the AMD AMI maker. -- Rafal Lukawiecki Data Scientist=20 Project Botticelli Ltd=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74098FC7-FEF4-4940-A405-76231A7686AF>