[BUG] Read-only durability verification requires a write marker #161

Open
opened 2026-10-17 20:23:06 +02:00 by erikinkinen · 1 comment
Owner

Summary

The read-only durability VM passes its guest checks, but the host media verifier
then requires an HTree file that only a writable scenario creates. The successful
read-only case is reported as failed.

Reproduction

Run ./scripts/run-scenario.sh tests/scenarios/subsystem-block-durability-readonly-positive.toml
on the selected Integration source graph. Original CI run 2822 reproduces the
failure with fs-ext4-large-dir, e2fs-fat-readonly and read-only QEMU media.

Expected and actual behavior

Read-only verification must retain the host file, depth-2 directory structure,
media integrity, durability rejection and readiness checks. It must not require
a guest-created mutation marker. Writable scenarios must still require that marker.

The original VM and marker assertions pass. The host then reports
error: storage ext HTree marker verification failed and returns status 1.

Environment and identity

  • Integration: f06bf72280eff2f49248ce816c327f8a3760a4f4, original run 2822,
    VM job 48883, task 35275, attempt 1.
  • Scenario: subsystem-block-durability-readonly-positive; worker 10.
  • Runtime configuration: tests/runtime-configs/runtime.dev.storage-readonly-ext.toml;
    release fixture, one CPU, 120-second VM limit and read-only block media.
  • Last known working revision: not established.

Evidence and prior checks

Integration CI 2822
records bootloader vm test passed, then
marker assertions passed, followed by the host HTree error. The verifier sets
expect_vfs_mutations=0 for e2fs-fat-readonly. Its FAT and ext mutation checks
respect that selection, but its HTree mutation check does not.

The retained terminal catalog result is 511 passed and 14 failed out of 525.
This report concerns the read-only host-verifier failure only.

Tracking

Related: read-only image host-file selection.
That earlier defect is separate from the host verifier requiring a new write.

  • Gate only the guest-written HTree marker on the existing mutation selection.
  • Cover read-only absence, writable absence and writable presence through the actual verifier.
  • Confirm the unchanged read-only guest and host checks pass together.
## Summary The read-only durability VM passes its guest checks, but the host media verifier then requires an HTree file that only a writable scenario creates. The successful read-only case is reported as failed. ## Reproduction Run `./scripts/run-scenario.sh tests/scenarios/subsystem-block-durability-readonly-positive.toml` on the selected Integration source graph. Original CI run 2822 reproduces the failure with `fs-ext4-large-dir`, `e2fs-fat-readonly` and read-only QEMU media. ## Expected and actual behavior Read-only verification must retain the host file, depth-2 directory structure, media integrity, durability rejection and readiness checks. It must not require a guest-created mutation marker. Writable scenarios must still require that marker. The original VM and marker assertions pass. The host then reports `error: storage ext HTree marker verification failed` and returns status 1. ## Environment and identity - Integration: `f06bf72280eff2f49248ce816c327f8a3760a4f4`, original run 2822, VM job 48883, task 35275, attempt 1. - Scenario: `subsystem-block-durability-readonly-positive`; worker 10. - Runtime configuration: `tests/runtime-configs/runtime.dev.storage-readonly-ext.toml`; release fixture, one CPU, 120-second VM limit and read-only block media. - Last known working revision: not established. ## Evidence and prior checks [Integration CI 2822](https://git.erikinkinen.fi/erix/integration/actions/runs/2822) records `bootloader vm test passed`, then `marker assertions passed`, followed by the host HTree error. The verifier sets `expect_vfs_mutations=0` for `e2fs-fat-readonly`. Its FAT and ext mutation checks respect that selection, but its HTree mutation check does not. The retained terminal catalog result is 511 passed and 14 failed out of 525. This report concerns the read-only host-verifier failure only. ## Tracking Related: [read-only image host-file selection](https://git.erikinkinen.fi/erix/integration/issues/158). That earlier defect is separate from the host verifier requiring a new write. - [x] Gate only the guest-written HTree marker on the existing mutation selection. - [x] Cover read-only absence, writable absence and writable presence through the actual verifier. - [ ] Confirm the unchanged read-only guest and host checks pass together.
Author
Owner

The guard and all eight host regressions pass at 05a511ec. Read-only absence succeeds, writable absence still fails, and writable presence succeeds; the negative controls also preserve the depth-two directory, original host entry, FAT/ext markers and large-file checks.

The first two criteria are checked. The unchanged read-only VM and host verification still need to pass together, so this issue remains open. The later worker-cache metadata collision is tracked separately in #163.

The guard and all eight host regressions pass at [05a511ec](https://git.erikinkinen.fi/erix/integration/commit/05a511ec958ce0cfa7f0486b9eb11f14c40dac73). Read-only absence succeeds, writable absence still fails, and writable presence succeeds; the negative controls also preserve the depth-two directory, original host entry, FAT/ext markers and large-file checks. The first two criteria are checked. The unchanged read-only VM and host verification still need to pass together, so this issue remains open. The later worker-cache metadata collision is tracked separately in [#163](https://git.erikinkinen.fi/erix/integration/issues/163).
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:19 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#161
No description provided.