WIP: Cover large-cluster exFAT allocation clearing #259

Draft
erikinkinen wants to merge 3 commits from feature/selected-exfat-large-cluster-media into feature/ram-entry-capacity-lifetimes
Owner

Add a 128-KiB exFAT cluster fixture with poisoned free storage. Check the physical allocation tail through sector 255 after the existing storage workload, and keep the declared filesystem extent separate from device padding.

Depends on #256 and Fatd #33. Refs #65.

  • Encode coherent large-cluster media and preserve the existing small-cluster fixture.
  • Add physical-tail observations and the selected VM scenario.
  • Execute the scenario on the coherent guest image.
Add a 128-KiB exFAT cluster fixture with poisoned free storage. Check the physical allocation tail through sector 255 after the existing storage workload, and keep the declared filesystem extent separate from device padding. Depends on [#256](https://git.erikinkinen.fi/erix/integration/pulls/256) and [Fatd #33](https://git.erikinkinen.fi/erix/fatd/pulls/33). Refs #65. - [x] Encode coherent large-cluster media and preserve the existing small-cluster fixture. - [x] Add physical-tail observations and the selected VM scenario. - [ ] Execute the scenario on the coherent guest image.
erikinkinen added this to the Alpha 1 milestone 2026-10-31 05:00:28 +01:00
test: Cover large-cluster exFAT allocation clearing
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (push) Successful in 4s
CI / rust (push) Failing after 25s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / integration (push) Has been skipped
5448e37330
Poison free storage in an explicitly sized 128-KiB cluster fixture and inspect physical slack through the final sector. Keep the existing writable storage route and declare only the real cluster heap, with the remaining device bytes treated as padding.
ci: Use shared development dependency profiles
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / integration (push) Has been cancelled
CI / markdown (push) Has been cancelled
b0bcc88000
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 / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (push) Successful in 14s
CI / rust (push) Failing after 1m22s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / integration (push) Has been skipped
34398ae455
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.
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (push) Successful in 14s
CI / rust (push) Failing after 1m22s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / integration (push) Has been skipped
This pull request has changes conflicting with the target branch.
  • .github/workflows/ci.yml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/selected-exfat-large-cluster-media:feature/selected-exfat-large-cluster-media'
git switch 'feature/selected-exfat-large-cluster-media'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/ram-entry-capacity-lifetimes'
git merge --no-ff 'feature/selected-exfat-large-cluster-media'
git switch 'feature/selected-exfat-large-cluster-media'
git rebase 'feature/ram-entry-capacity-lifetimes'
git switch 'feature/ram-entry-capacity-lifetimes'
git merge --ff-only 'feature/selected-exfat-large-cluster-media'
git switch 'feature/selected-exfat-large-cluster-media'
git rebase 'feature/ram-entry-capacity-lifetimes'
git switch 'feature/ram-entry-capacity-lifetimes'
git merge --no-ff 'feature/selected-exfat-large-cluster-media'
git switch 'feature/ram-entry-capacity-lifetimes'
git merge --squash 'feature/selected-exfat-large-cluster-media'
git switch 'feature/ram-entry-capacity-lifetimes'
git merge --ff-only 'feature/selected-exfat-large-cluster-media'
git switch 'feature/ram-entry-capacity-lifetimes'
git merge 'feature/selected-exfat-large-cluster-media'
git push origin 'feature/ram-entry-capacity-lifetimes'
Sign in to join this conversation.
No description provided.