Persist complete journal operations in original order #45

Manually merged
erikinkinen merged 15 commits from feature/ext-journal-operation-order into feature/ext-fixed-entry-authority 2026-11-13 20:51:50 +01:00
Owner

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.

  • Implement complete-operation publication and explicit original-route barriers.
  • Preserve committed-prefix admission, revocation and full/fast recovery ownership.
  • Add independent volatile/stable interruption controls.
  • Complete component and on-media acceptance.
  • Retain failed callback I/O members and refuse a partial commit.
  • Keep concurrent filesystem checker inputs independently owned.

Compatibility fsync/fdatasync and release-image power-loss acceptance remain separate.

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](https://git.erikinkinen.fi/erix/lib-block/pulls/5). Cargo declarations track main; the component profile selects the complete public cohort. - [x] Implement complete-operation publication and explicit original-route barriers. - [x] Preserve committed-prefix admission, revocation and full/fast recovery ownership. - [x] Add independent volatile/stable interruption controls. - [x] Complete component and on-media acceptance. - [x] Retain failed callback I/O members and refuse a partial commit. - [x] Keep concurrent filesystem checker inputs independently owned. Compatibility fsync/fdatasync and release-image power-loss acceptance remain separate.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 12:21:39 +01:00
fix: Persist complete journal operations in original order
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 5s
CI / test (push) Failing after 1m9s
28ebade132
Persist complete journal operations in original order.
Retain original filesystem bounds in journal staging.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (push) Has been cancelled
CI / markdown (push) Has been cancelled
cd50a44ee6
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Declare policy helper and output boundaries
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 9s
CI / test (push) Failing after 4m1s
bac29166ff
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Bring current retained-entry custody, raw basename handling and represented inode checksums into the journal-ordering feature while preserving its complete transaction and persistence implementation.

# Conflicts:
#	.github/workflows/ci.yml
#	ARCHITECTURE.md
#	README.md
#	ROADMAP.md
Select the complete public journal, IPC and owned-crypto participants through an explicit component profile while Cargo declarations track main. Preserve strict original host, freestanding, on-media and documentation gates, and distinguish host persistence controls from release-image acceptance.
docs: Keep journal persistence boundaries readable
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Failing after 2m30s
d0b5be1033
Shorten table labels without changing the required original-device persistence states and identify the journal cohort explicitly.
Require the original complete-operation owner to retain a refused member even if the callback returns success, leaving earlier staged filesystem blocks unpublished.
Declare write-through ownership in the original dispatch media fixture. Record actual payload sector addresses and barriers, distinguish journal payload from home checkpoint writes using the resulting inode map, and require one complete commit between their persistence boundaries.
Latch the original callback I/O refusal, reject subsequent valid backend I/O and prevent callback success from committing an earlier staged prefix. Preserve each local range and route refusal, leave persistence with the outer owner and refuse checkpointing a failed staged operation. Refs #17.
Inject failure before and after the original journal cache changes, then prove that swallowed errors cannot perform more callback I/O, mutate output buffers or publish an earlier filesystem prefix. Keep cleanup on the original outer owner and compare persisted media independently.
test: Cover failed staging custody on both original journal forms
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Failing after 48s
bd811e43c6
Exercise lost write completions before and after cache mutation on internal and external journal routes. Reuse the independent internal inode fixture, compare home bytes outside the real internal log extent, and document the complete-operation failure fence.
fix: Preserve checked observer indices and original journal errors
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Failing after 2m31s
c529f183a6
Use the block mapper’s checked logical index type and retain callback failure codes without transforming their results.
Use the shared process-wide temporary image allocator instead of format/PID-only or fixed paths. Exercise repeated simultaneous checks of the same filesystem format so one operation cannot remove another checker’s original input, while preserving all on-media assertions and parallel execution.
test: Retire successful checker images through their own paths
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 2m39s
9767af2fe8
Remove each uniquely owned image after its independent checks succeed, retaining failed inputs for diagnosis without accumulating successful temporary media.
chore: Merge the checker ownership prerequisite
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 2m40s
ec9d6a8533
Include the corrected retained-entry test ancestry after its complete component qualification, preserving the journal implementation and its independently qualified source tree.
erikinkinen changed title from WIP: Persist complete journal operations in original order to Persist complete journal operations in original order 2026-11-13 11:24:24 +01:00
Author
Owner

Completed 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.

Completed 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](https://git.erikinkinen.fi/erix/e2fsd/actions/runs/689) pass. Compatibility persistence controls follow in #46. Release-image and hardware power-loss acceptance remain separate.
erikinkinen manually merged commit cf8cf81edd into feature/ext-fixed-entry-authority 2026-11-13 20:51:50 +01:00
Sign in to join this conversation.
No description provided.