From 505f20a67b7448f332704d03ab3ceb0b83a0bf87 Mon Sep 17 00:00:00 2001 From: Glen Barber Date: Mon, 28 Aug 2017 14:49:26 +0000 Subject: [PATCH] Increase the Amazon EC2 AMI image size from 2GB to 3GB to prevent image build failures due to a full md(4)-backed filesystem. Sponsored by: The FreeBSD Foundation --- release/tools/ec2.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/release/tools/ec2.conf b/release/tools/ec2.conf index 4a7a1e809ec7..924e7876001d 100644 --- a/release/tools/ec2.conf +++ b/release/tools/ec2.conf @@ -11,12 +11,12 @@ export VM_EXTRA_PACKAGES="ec2-scripts firstboot-freebsd-update firstboot-pkgs du # Set to a list of third-party software to enable in rc.conf(5). export VM_RC_LIST="ec2_configinit ec2_fetchkey ec2_ephemeralswap ec2_loghostkey firstboot_freebsd_update firstboot_pkgs" -# Build with a 2 GB UFS partition; the growfs rc.d script will expand +# Build with a 3 GB UFS partition; the growfs rc.d script will expand # the partition to fill the root disk after the EC2 instance is launched. # Note that if this is set to G, we will end up with an GB disk # image since VMSIZE is the size of the UFS partition, not the disk which # it resides within. -export VMSIZE=2048M +export VMSIZE=3072M # No swap space; the ec2_ephemeralswap rc.d script will allocate swap # space on EC2 ephemeral disks. (If they exist -- the T2 low-cost instances