From 6b9913f01091a3ae52d70439bc49c8eb23e32fb8 Mon Sep 17 00:00:00 2001 From: Gunnar Beutner Date: Sat, 19 Feb 2022 10:38:16 +0100 Subject: [PATCH] Meta: Explicitly set number of available inodes for genext2fs According to its manpage genext2fs tries to create the file system with as few inodes as possible. This causes SerenityOS to fail at boot time when creating temporary files. --- Meta/build-image-qemu.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Meta/build-image-qemu.sh b/Meta/build-image-qemu.sh index bd10030e41..d9018a33f9 100755 --- a/Meta/build-image-qemu.sh +++ b/Meta/build-image-qemu.sh @@ -191,7 +191,7 @@ if [ $use_genext2fs = 1 ]; then # genext2fs is very slow in generating big images, so I use a smaller image here. size can be updated # if it's not enough. # not using "-I $INODE_SIZE" since it hangs. Serenity handles whatever default this uses instead. - genext2fs -B 4096 -b $((DISK_SIZE_BYTES / 4096)) -d mnt _disk_image || die "try increasing image size (genext2fs -b)" + genext2fs -B 4096 -b $((DISK_SIZE_BYTES / 4096)) -N $INODE_COUNT -d mnt _disk_image || die "try increasing image size (genext2fs -b)" # if using docker with shared mount, file is created as root, so make it writable for users chmod 0666 _disk_image fi