[FEATURE] Persist original POSIX metadata with atomic FAT-family updates #8
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/fatd#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem and motivation
FAT/exFAT native observations intentionally lack original POSIX identity, owner,
mode, link and change-time evidence. Entry coordinates and clusters cannot replace
persistent object serials, and mount/status clocks cannot reconstruct historical
time. Complete status and permission mediation needs an explicit persistent source
joined atomically to the original filesystem mutations.
Proposed behavior and scope
Implement an administrator-selected FAT-family metadata extension inside the
original partition and outside its declared file-data volume. Selection is explicit
through the existing mount-control route. Existing imported media keeps its honest
unknown fields; ordinary file bytes never opt a mount into a new metadata policy.
A versioned checksummed immutable footer at the final original partition block
binds the original block width, FAT/exFAT volume length, metadata extent, journal
extent and nonzero filesystem serial. All extents must fit the same original
partition. The metadata extent begins at the end of the declared volume, remains
inside the journal target prefix, and ends before the disjoint journal. The footer
is outside both writable target and journal extents. Require exact geometry and
canonical reserved bytes before any recovery or filesystem repair.
The metadata catalog retains a nonwrapping object-serial allocator and original
root/object records. Records bind separately allocated serials to exact original
entry geometry and checked original entry evidence; geometry is a lookup key,
never the serial. Retain complete mode, original UID/GID, actual links and
independent 24-byte signed source/precision-qualified event observations. No
recipient identity, path, cluster, handle, mount time or newly queried status clock
can fill a missing original fact. Preserve imported local FAT time as unknown UTC
unless original qualified evidence exists. Birth is not a prerequisite for POSIX
status. The extension's initial policy is explicit mode/ownership with known ACL
absence; later ACL support must be explicit and cannot silently reinterpret media.
Use the implemented original-device undo adapter to join normal FAT/exFAT writes
and metadata changes. Reserve original mount state and reply capacity first, then
admit explicit extension geometry and recover before normal mount validation can
repair mirrors. Complete validation and metadata publication follow recovery.
Mount-level read-only selection independently prohibits recovery writes, even on a
physically writable device. Metadata and journal sectors are excluded from the
ordinary filesystem view. No automatic formatting or older-format fallback.
One provider operation owns one transaction across nested timestamped, exact-entry
and ordinary helpers. Preserve all pre-effect admission. Failed block operations
cannot be swallowed, and storage uncertainty fails stopped without an ordinary
reply. On known rollback, restore affected volatile object state without reviving
consumed navigation evidence, cleanup keys or monotonic identities. Reserve any
rollback storage through the existing deployment arena; do not impose a fixed
record ceiling. Original mount/handle retirement must clear new policy state.
Implement shared ordinary/acquired status and permission observations, actual
creation attribution, event updates, rename/replacement/deletion/reuse and alias
lifetime under this transaction policy. New format selection is not full feature
acceptance until these consumers and native workloads are integrated.
Authority, security and reliability
Source authority remains the existing administrator mount route and the original
retained block device. New fields are descriptive policy and geometry, never a
capability grant or an alternate endpoint selector. An on-media record cannot
address another device or an extent outside those already admitted. Scope,
read-only ceilings, one-use permission evidence and original cleanup remain in
force. Checksums establish corruption detection, not authentication against a
malicious storage owner. The explicit mount owner selects this persistent source.
Require complete prefix/recovery admission, reject corrupt or missing selected
metadata, and never substitute plausible defaults. A reopened owner must recover
uncertain original media before ordinary use. Copies of volatile state cannot
restore spent authority-bearing keys or evidence. Security, reliability and then
performance determine implementation choices. Derive capacity from actual media
and deployment storage, share codecs and avoid repeated whole-directory discovery.
No measured improvement is claimed without execution.
Acceptance criteria
Checklist
Alternatives and tradeoffs
Plain FAT/exFAT cannot supply the missing original fields. Import defaults and
clock queries at mount/status time would invent evidence. An ordinary sidecar file
would expose policy through file access and separate publication lifetimes. The
explicit original-partition extent avoids both. A generic journal alone cannot
restore provider caches or establish metadata provenance; its consumer integration
is part of this feature. Full record layout and indexed lookup are refined with
provider invariants before their source changes; no alternate authority or fixed
catalog ceiling is introduced for convenience.
Tracking and rollout
Implemented and closed under source acceptance; test and CI execution remain waived.
Complete original metadata and status/directory source acceptance — 1 October 2026
Source acceptance covers explicit format admission/recovery, persistent original identities and full metadata, shared ordinary/acquired observations, fresh permissions, atomic filesystem/catalog updates, alias and cleanup lifetime, compatibility stat families and shared seekable directory descriptions. Imported unavailable facts remain explicit refusals.
Runtime and independent fixture producers emit the mandatory stream allocation flag, which admission and image verification require.
This checkpoint authors 14 Rust and four Python controls plus two selected exFAT VM scenarios; two existing FAT scenarios now also require six-child directory growth, post-growth observations and complete cleanup.
Both complete EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue from erix/blockd2026-09-30 23:23:21 +02:00
erikinkinen referenced this issue from erix/coreutils2026-09-30 23:23:29 +02:00
erikinkinen referenced this issue from erix/crashd2026-09-30 23:23:41 +02:00
erikinkinen referenced this issue from erix/deviced2026-09-30 23:23:47 +02:00
erikinkinen referenced this issue from erix/docs2026-09-30 23:23:56 +02:00
erikinkinen referenced this issue from erix/drv-acpi2026-09-30 23:24:06 +02:00
erikinkinen referenced this issue from erix/drv-i80422026-09-30 23:24:09 +02:00
erikinkinen referenced this issue from erix/drv-ps2-keyboard2026-09-30 23:24:15 +02:00
erikinkinen referenced this issue from erix/drv-ps2-mouse2026-09-30 23:24:21 +02:00
erikinkinen referenced this issue from erix/drv-rtc-cmos2026-09-30 23:24:23 +02:00
erikinkinen referenced this issue from erix/drv-serial2026-09-30 23:24:25 +02:00
erikinkinen referenced this issue from erix/drv-virtio-block2026-09-30 23:24:30 +02:00
erikinkinen referenced this issue from erix/dynlinkd2026-09-30 23:24:33 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-30 23:24:34 +02:00
erikinkinen referenced this issue from erix/exsh2026-09-30 23:24:36 +02:00
erikinkinen referenced this issue from erix/extop2026-09-30 23:24:37 +02:00
erikinkinen referenced this issue2026-09-30 23:24:37 +02:00
erikinkinen referenced this issue from erix/fbcond2026-09-30 23:24:38 +02:00
erikinkinen referenced this issue from erix/hotplugd2026-09-30 23:24:39 +02:00
erikinkinen referenced this issue from erix/inputd2026-09-30 23:24:40 +02:00
erikinkinen referenced this issue from erix/integration2026-09-30 23:24:41 +02:00
erikinkinen referenced this issue from erix/irqd2026-09-30 23:24:43 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-30 23:24:44 +02:00
erikinkinen referenced this issue from erix/keyd2026-09-30 23:24:45 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-30 23:24:45 +02:00
erikinkinen referenced this issue from erix/lib-block2026-09-30 23:24:47 +02:00
erikinkinen referenced this issue from erix/lib-bootstrap2026-09-30 23:24:48 +02:00
erikinkinen referenced this issue from erix/lib-capabi2026-09-30 23:24:49 +02:00
erikinkinen referenced this issue from erix/lib-driver2026-09-30 23:24:50 +02:00
erikinkinen referenced this issue from erix/lib-input2026-09-30 23:24:51 +02:00
erikinkinen referenced this issue from erix/lib-interrupt2026-09-30 23:24:52 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-30 23:24:54 +02:00
erikinkinen referenced this issue from erix/lib-log2026-09-30 23:24:55 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-30 23:24:56 +02:00
erikinkinen referenced this issue from erix/lib-service2026-09-30 23:24:57 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-09-30 23:24:59 +02:00
erikinkinen referenced this issue from erix/lib-time2026-09-30 23:25:00 +02:00
erikinkinen referenced this issue from erix/lib-tty2026-09-30 23:25:01 +02:00
erikinkinen referenced this issue from erix/lib-vfs2026-09-30 23:25:02 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-30 23:25:03 +02:00
erikinkinen referenced this issue from erix/logd2026-09-30 23:25:03 +02:00
erikinkinen referenced this issue from erix/memd2026-09-30 23:25:04 +02:00
erikinkinen referenced this issue from erix/named2026-09-30 23:25:05 +02:00
erikinkinen referenced this issue from erix/pagerd2026-09-30 23:25:06 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-30 23:25:07 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-09-30 23:25:08 +02:00
erikinkinen referenced this issue from erix/probed2026-09-30 23:25:09 +02:00
erikinkinen referenced this issue from erix/procd2026-09-30 23:25:10 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-30 23:25:10 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-30 23:25:11 +02:00
erikinkinen referenced this issue from erix/seriald2026-09-30 23:25:12 +02:00
erikinkinen referenced this issue from erix/timed2026-09-30 23:25:12 +02:00
erikinkinen referenced this issue from erix/ttyd2026-09-30 23:25:13 +02:00
erikinkinen referenced this issue from erix/vfsd2026-09-30 23:25:13 +02:00
erikinkinen referenced this issue from erix/vspaced2026-09-30 23:25:14 +02:00