disk_layout: bump stateful partition size
Some builds are dangerously close to the 2 GiB limitation. For instance,
picking up an Octopus R80-12709.0.0 image shows only 77 MiB free:
$ df -h dir_1/
Filesystem Size Used Avail Use% Mounted on
/dev/loop1p1 2.0G 1.9G 77M 97% /mnt/host/source/src/scripts/octopus-R80-12709.0.0/dir_1
This partition size isn't magical either, since we're currently well
below the 8 GiB requirement (e.g., for USB disks) but still above 4 GiB:
$ /sbin/fdisk -l chromiumos_test_image.bin
Disk chromiumos_test_image.bin: 4.5 GiB, 4861278720 bytes, 9494685 sectors
Units: sectors of 1 * 512 = 512 bytes
[...]
And finally, disk images are sparse, so bumping this limit shouldn't
cause any additional disk usage until we actually add packages that use
the space.
3 GiB is an arbitrary increase from 2 GiB that happens to be easy to
type.
BUG=none
TEST=`./build_image [...] test`
Change-Id: Iba40692757a4fa5dab5274269ef7b1e98bd91981
Exempt-From-Owner-Approval: Often breaks CQ
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosutils/+/1935408
Commit-Queue: Nicolas Boichat <drinkcat@chromium.org>
Tested-by: Nicolas Boichat <drinkcat@chromium.org>
Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-by: Nicolas Boichat <drinkcat@chromium.org>
2 files changed
