Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ext2FS: Lazy block allocation and holes #6236

Open
awesomekling opened this issue Apr 11, 2021 · 0 comments · May be fixed by #24149
Open

Ext2FS: Lazy block allocation and holes #6236

awesomekling opened this issue Apr 11, 2021 · 0 comments · May be fixed by #24149
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@awesomekling
Copy link
Member

Block allocation in Ext2FS is currently eager (all blocks are immediately allocated when file size changes.)

This makes something like truncate -s 50000000 take a long time, while it's instant on other systems.

We should defer block allocation to when a block is actually written to instead. Making an inode larger should only update the size field.
@awesomekling awesomekling added the enhancement New feature or request label Apr 11, 2021
@bgianfo bgianfo added the help wanted Extra attention is needed label May 10, 2021
@implicitfield implicitfield linked a pull request Apr 28, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Kernel/Ext2FS: Allocate blocks lazily + support writing holes implicitfield/serenity
2 participants
@bgianfo @awesomekling