Preserve ext extent length and endpoint boundaries #47
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/e2fsd!47
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/ext-extent-allocation-boundaries"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Preserve the full initialized/unwritten extent encodings and final logical block across lookup, rebuild, reclamation and fast-commit replay. Sparse growth walks existing mappings once, and file-size admission follows the complete original extent or legacy tree.
Shared inode accounting preserves sector/filesystem-block units and publishes required representation features in the same transaction. Bigalloc fragments retain their original allocation identity across gap filling, shrink and whole-tree reclamation.
Depends on #46. Fixes #18 and #19.
Encrypted growth, compatibility resize/sync serving and release-image workloads retain their separate acceptance requirements.
WIP: Preserve ext extent length and endpoint boundariesto Preserve ext extent length and endpoint boundariesThe complete extent, file-size and allocation-unit feature is ready for review. Final logical blocks and maximum extent encodings survive actual replay and reclamation. ACL preflights now use the same representation limits as inode publication, preserving refusal before allocation at the real huge-unit boundary.