thaloco/banger
1
Fork 0
Code Pull requests Releases Packages Activity Actions

system: mkfs work disks with lazy_itable_init + lazy_journal_init

Browse source 
mkfs.ext4 zeroes the entire inode table and journal at format time
unless told otherwise. On an 8 GiB work disk that's roughly 500-700ms
of host CPU/IO per 'banger vm create', for a one-time small per-write
penalty inside the guest the first time it touches an unwritten
inode that nobody can perceive.

Centralise the canonical mkfs -E option list as
system.MkfsExtraOptions and use it everywhere banger calls mkfs.ext4
on a VM-internal image: the no-seed work disk, MaterializeWorkDisk,
BuildWorkSeedImage, and the imagepull rootfs builder. The work-disk
paths feed vm create directly; the others are one-off but still
benefit from the faster format.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Thales Maciel 2026-04-26 21:32:57 -03:00
parent 74e5a7cedb
commit 74a2d064fd
No known key found for this signature in database
GPG key ID: 33112E6833C34679
3 changed files with 18 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
internal/imagepull/ext4.go
View file

@ -64,7 +64,7 @@ func BuildExt4(ctx context.Context, runner system.CommandRunner, srcDir, outFile
"-q",
"-d", srcDir,
"-L", "banger-rootfs",
"-E", "root_owner=0:0",
"-E", system.MkfsExtraOptions,
outFile,
)
if runErr != nil {