[BUG] FAT catalog VM case omits its required catalog witness #124

Open
opened 2026-10-14 22:21:36 +02:00 by erikinkinen · 3 comments
Owner

Summary

The FAT catalog VM case reaches ordinary storage readiness without its required catalog witness. This prevents the full VM catalog from passing. The same failure appears in two original runs; it predates the current Vfsd read-path repair.

Reproduction

The complete catalog in Integration run 2639 includes subsystem-fat-catalog-clean-positive. Its maintained isolated entry point is:

bash scripts/run-scenario.sh tests/scenarios/subsystem-fat-catalog-clean-positive.toml components.toml

The observations come from the original workflows. An isolated reproduction and failure rate have not been established.

Expected and actual behavior

Expected: the case emits ERIX_ROOTD:TRACE:VFS:FAT_CATALOG_OK and ERIX_ROOTD:TRACE:VFS:FAT_DIRECTORY_GROWTH_OK, reaches all declared readiness markers and exits with the expected guest code 0x10.

Actual: at 19:40:27 UTC on 14 October, worker 0 reports required marker missing: ERIX_ROOTD:TRACE:VFS:FAT_CATALOG_OK. Its retained serial context includes ordinary VFS I/O, storage readiness and final Rootd readiness. The complete run ends with 435 passed and 90 failed cases out of 525.

Environment and identity

  • Source graph: Integration 9e9e942c, Rootd 596e8cd6, Vfsd a2b5ef91, Fatd dfba7769.
  • Full-system image built with the Rust release profile and development runtime configuration, e2fs-fat Rootd mode, writable fs-fat-undo-clean fixture and runtime.dev.fat-undo-writable.toml. The /boot mount explicitly selects FAT metadata. A complete image digest is not established by this report.
  • x86_64 QEMU with KVM available, one vCPU per case and 12 catalog workers. The job installed Debian QEMU package 1:10.0.13+ds-0+deb13u1 and used rust:latest; an exact compiler and firmware version has not been retained here.
  • The existing administrator-selected mount and retained filesystem routes supply the workload authority. No additional rights or relaxed acceptance limits are requested.
  • Last known passing revision: unknown.

Evidence and prior checks

Original run 2630 at Integration b0cea358 reports the same case and missing witness at 16:59:00 UTC. Both runs have the same 90 failed case paths. The scenario, mount configuration, FAT catalog fixture and witness producer are unchanged between those source graphs.

The witness is emitted only after full-width owner/mode/timestamp checks and temporary-file cleanup. The original serial context does not locate the failure. Source review identifies a completion-route defect: the successful FAT verifiers submit these markers through diagnostic tracing after Rootd retires direct-kernel logging. The source repair uses the retained live Logd route after each verifier succeeds. Existing limits remain 600 seconds for image preparation, 120 seconds for QEMU and 45 seconds without serial progress.

Tracking

Related work: FAT metadata implementation, phase completion. Existing FAT32 metadata and exFAT deadline reports concern different cases and errors.

  • Identify the point where the selected catalog workload loses its required witness.
  • Repair the owning source or fixture while preserving explicit mount selection and full-width metadata.
  • Demonstrate both catalog witnesses in the original case and retain the full catalog result.
## Summary The FAT catalog VM case reaches ordinary storage readiness without its required catalog witness. This prevents the full VM catalog from passing. The same failure appears in two original runs; it predates the current Vfsd read-path repair. ## Reproduction The complete catalog in [Integration run 2639](https://git.erikinkinen.fi/erix/integration/actions/runs/2639) includes `subsystem-fat-catalog-clean-positive`. Its maintained isolated entry point is: ```sh bash scripts/run-scenario.sh tests/scenarios/subsystem-fat-catalog-clean-positive.toml components.toml ``` The observations come from the original workflows. An isolated reproduction and failure rate have not been established. ## Expected and actual behavior Expected: the case emits `ERIX_ROOTD:TRACE:VFS:FAT_CATALOG_OK` and `ERIX_ROOTD:TRACE:VFS:FAT_DIRECTORY_GROWTH_OK`, reaches all declared readiness markers and exits with the expected guest code `0x10`. Actual: at 19:40:27 UTC on 14 October, worker 0 reports `required marker missing: ERIX_ROOTD:TRACE:VFS:FAT_CATALOG_OK`. Its retained serial context includes ordinary VFS I/O, storage readiness and final Rootd readiness. The complete run ends with 435 passed and 90 failed cases out of 525. ## Environment and identity - Source graph: [Integration 9e9e942c](https://git.erikinkinen.fi/erix/integration/commit/9e9e942ce68171e17ee848e9d66db4b365814a90), Rootd `596e8cd6`, Vfsd `a2b5ef91`, Fatd `dfba7769`. - Full-system image built with the Rust release profile and development runtime configuration, `e2fs-fat` Rootd mode, writable `fs-fat-undo-clean` fixture and `runtime.dev.fat-undo-writable.toml`. The `/boot` mount explicitly selects FAT metadata. A complete image digest is not established by this report. - x86_64 QEMU with KVM available, one vCPU per case and 12 catalog workers. The job installed Debian QEMU package `1:10.0.13+ds-0+deb13u1` and used `rust:latest`; an exact compiler and firmware version has not been retained here. - The existing administrator-selected mount and retained filesystem routes supply the workload authority. No additional rights or relaxed acceptance limits are requested. - Last known passing revision: unknown. ## Evidence and prior checks [Original run 2630](https://git.erikinkinen.fi/erix/integration/actions/runs/2630) at Integration `b0cea358` reports the same case and missing witness at 16:59:00 UTC. Both runs have the same 90 failed case paths. The scenario, mount configuration, FAT catalog fixture and witness producer are unchanged between those source graphs. The witness is emitted only after full-width owner/mode/timestamp checks and temporary-file cleanup. The original serial context does not locate the failure. Source review identifies a completion-route defect: the successful FAT verifiers submit these markers through diagnostic tracing after Rootd retires direct-kernel logging. The source repair uses the retained live Logd route after each verifier succeeds. Existing limits remain 600 seconds for image preparation, 120 seconds for QEMU and 45 seconds without serial progress. ## Tracking Related work: [FAT metadata implementation](https://git.erikinkinen.fi/erix/fatd/issues/8), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Existing FAT32 metadata and exFAT deadline reports concern different cases and errors. - [x] Identify the point where the selected catalog workload loses its required witness. - [x] Repair the owning source or fixture while preserving explicit mount selection and full-width metadata. - [ ] Demonstrate both catalog witnesses in the original case and retain the full catalog result.
Author
Owner

Rootd’s FAT completion markers used a diagnostic route that is retired after Logd starts. The repair submits each marker through the existing live Logd route after its verifier succeeds and stops if verification or submission fails. The original guest case and its acceptance limits remain unchanged; guest confirmation is pending.

Rootd’s FAT completion markers used a diagnostic route that is retired after Logd starts. [The repair](https://git.erikinkinen.fi/erix/rootd/commit/e64f15fb8d5c92784423729cb674f5e7c4960703) submits each marker through the existing live Logd route after its verifier succeeds and stops if verification or submission fails. The original guest case and its acceptance limits remain unchanged; guest confirmation is pending.
Author
Owner

The unchanged clean FAT case now reaches FAT_CATALOG_OK, FAT_DIRECTORY_GROWTH_OK and final readiness with Rootd e64f15fb. This result uses candidate catalogs with runtime 4f6eae96; the full catalog is still pending. The original image and QEMU limits are unchanged.

The unchanged clean FAT case now reaches `FAT_CATALOG_OK`, `FAT_DIRECTORY_GROWTH_OK` and final readiness with [Rootd e64f15fb](https://git.erikinkinen.fi/erix/rootd/commit/e64f15fb8d5c92784423729cb674f5e7c4960703). This result uses candidate catalogs with runtime `4f6eae96`; the full catalog is still pending. The original image and QEMU limits are unchanged.
Author
Owner

The unchanged clean FAT case passes on published 94802d9c with Rootd af0b4261. Catalog and directory-growth witnesses precede VFS I/O and final readiness. Its first execution exits zero after 264.4 seconds, with confirmed cleanup and no warnings. The full scenario catalog remains open.

The unchanged clean FAT case passes on published [94802d9c](https://git.erikinkinen.fi/erix/integration/commit/94802d9c1650821f8cdda36a49d84b91ffbf4c5e) with [Rootd af0b4261](https://git.erikinkinen.fi/erix/rootd/commit/af0b4261f878243af986214b9591b0c2c5b494d5). Catalog and directory-growth witnesses precede VFS I/O and final readiness. Its first execution exits zero after 264.4 seconds, with confirmed cleanup and no warnings. The full scenario catalog remains open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:16 +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#124
No description provided.