Persist complete journal operations in original order #45
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!45
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/ext-journal-operation-order"
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?
Persist each complete filesystem operation with one JBD2 transaction identity and commit, including operations spanning several descriptors. Keep publication, checkpoint and recovery barriers on the original filesystem and journal routes; retire full replay before fast-commit staging reuses the ring.
Refs #17. Depends on #44 and the original-device block journal supplier. Cargo declarations track main; the component profile selects the complete public cohort.
Compatibility fsync/fdatasync and release-image power-loss acceptance remain separate.
WIP: Persist complete journal operations in original orderto Persist complete journal operations in original orderCompleted at
ec9d6a85: whole-operation commits, original-route barriers, full/fast recovery retirement and first-failure custody are in place. The failure controls cover lost staging-write replies on internal and external journals; concurrent filesystem checks now retain distinct inputs. All 515 component tests and current CI pass.Compatibility persistence controls follow in #46. Release-image and hardware power-loss acceptance remain separate.