aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorColin Percival <cperciva@FreeBSD.org>2023-12-28 22:23:52 +0000
committerColin Percival <cperciva@FreeBSD.org>2023-12-28 22:24:46 +0000
commit8a735ffdf04936c6785ac4fa31486639262dd416 (patch)
tree4f07b96e24ef72f9aa754ae8b33ee1afd4268c37
parente7300a8f638e6eb801953c0fb9e53d99308dc3f0 (diff)
downloadsrc-8a735ffdf04936c6785ac4fa31486639262dd416.tar.gz
src-8a735ffdf04936c6785ac4fa31486639262dd416.zip
EC2: Bump AMI size to 6 GB
This week's cloud-init ZFS snapshots ran out of disk space.
-rw-r--r--release/tools/ec2.conf4
1 files changed, 2 insertions, 2 deletions
diff --git a/release/tools/ec2.conf b/release/tools/ec2.conf
index a233bf5981c1..f8bfe0911759 100644
--- a/release/tools/ec2.conf
+++ b/release/tools/ec2.conf
@@ -10,12 +10,12 @@ export VM_EXTRA_PACKAGES="${VM_EXTRA_PACKAGES} ebsnvme-id amazon-ssm-agent"
# Services which should be enabled by default in rc.conf(5).
export VM_RC_LIST="dev_aws_disk ntpd"
-# Build with a 4.9 GB partition; the growfs rc.d script will expand
+# Build with a 5.9 GB 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 <N>G, we will end up with an <N+1> GB disk
# image since VMSIZE is the size of the filesystem partition, not the disk
# which it resides within.
-export VMSIZE=5000m
+export VMSIZE=6000m
# No swap space; it doesn't make sense to provision any as part of the disk
# image when we could be launching onto a system with anywhere between 0.5