Retain FAT ancestry and explicit metadata observations #22
No reviewers
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!22
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/fat-retained-entry-observations"
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?
Retain original FAT/exFAT mount and component custody through independent cleanup, and observe directories through physical positions with admitted output and timestamp effects. Keep unavailable permission, inode and UTC evidence explicit. Committed writes and truncation keep aliases of the same mounted entry coherent.
Refs #1. Depends on #21 and erix/lib-ipc#111. Later native fixed-entry work remains in #27; this slice retains the earlier administrative interfaces.
WIP: Retained FAT ancestry, exact entries and honest metadata observationsto Retain FAT ancestry and explicit metadata observationsReady for review. The first-allocation alias regression is fixed: reads, writes and native size observations keep the original entry geometry while unrelated files remain untouched. Calendar persistence is checked separately from UTC availability on actual FAT and exFAT media. Guest and later interface-retirement acceptance remain separate.