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.
This commit is contained in:
parent
7a65bd8efb
commit
6b9913f010
Notes:
sideshowbarker
2024-07-17 18:32:42 +09:00
Author: https://github.com/gunnarbeutner Commit: https://github.com/SerenityOS/serenity/commit/6b9913f010 Pull-request: https://github.com/SerenityOS/serenity/pull/12648 Issue: https://github.com/SerenityOS/serenity/issues/12644 Reviewed-by: https://github.com/IdanHo ✅
1 changed files with 1 additions and 1 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue