Fsck and WAL
Explicit WAL replay and integrity-check scaffolding.
Write-ahead log
Wal::append stores a little-endian u32 length followed by a bincode WalEntry, then syncs the file. The entries cover namespace/policy/agent metadata and append accounting. Wal::replay passes decoded entries to the caller's closure.
StrandVault::new does not call replay_wal. If recovery needs that path, invoke it explicitly after selecting the intended log. The current vault replay updates in-memory agent records; namespace/policy entries are informational and append entries are no-ops. It does not reconstruct missing block payloads.
complete_append writes WAL accounting on a best-effort basis and does not propagate that WAL append failure. Do not use its successful return as proof of an independently durable recovery record.
Fsck
fsck::fsck(&provider) calls FsckProvider::list_strands_ids and check_strand, returning FsckReport { strands_checked, errors }. It collects failures; it does not automatically repair blocks. Supply an integrity checker appropriate to the backend and inspect the report even when the wrapper returns Ok.
WAL declarations · Fsck declarations.
Source reference
Exact declarations and source provenance · Package features and manifest.
