diff options
| author | Jo-Philipp Wich <jo@mein.io> | 2016-10-16 01:59:44 +0200 |
|---|---|---|
| committer | Jo-Philipp Wich <jo@mein.io> | 2016-10-27 19:24:38 +0200 |
| commit | dc6cc040169a3f29d0126c24d65d5e7b6c479ab8 (patch) | |
| tree | aa7c70ae3428ead120c1ba91eb1ff1fc7dc45501 /scripts/brcmImage.pl | |
| parent | d1ae4c4958e6394a0f00be334bc045bce9f0614d (diff) | |
| download | upstream-dc6cc040169a3f29d0126c24d65d5e7b6c479ab8.tar.gz upstream-dc6cc040169a3f29d0126c24d65d5e7b6c479ab8.tar.bz2 upstream-dc6cc040169a3f29d0126c24d65d5e7b6c479ab8.zip | |
config: ext4: increase x86 rootfs size to 2GB to support online resize2fs
The current default rootfs size of 256MB in conjunction with 4K blocks
produces an ext4 filesystem which lacks the appropriate amount of backup GDT
entries to support online-resizing.
For x86 targets, increase the default rootfs size to 2048MB which allows
online resizing the filesystem to up to 2TB which is the current theoretical
maximum for LEDE, due to missing GPT support on the root block device.
Note that the filesystem artefact will not occupy 2GB on the build system as
the make_ext4fs utility uses sparse files to generate the filesystem images,
so the actual disk usage is much lower. Furthermore the filesystem images
are gzip compressed, shrinking them to only a few megabytes on the download
server.
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Acked-by: Michael Heimpold <mhei@heimpold.de>
Diffstat (limited to 'scripts/brcmImage.pl')
0 files changed, 0 insertions, 0 deletions