Expand description
The filesystem-agnostic value types the FUSE/Dokan mount layer speaks.
These are 4n6mount’s own FUSE-facing vocabulary — a small, u64-inode,
serde-friendly model that the mount callbacks (getattr/readdir/read/…)
consume directly. A concrete backend (the memory VFS, or the disk-image
EngineFs adapter over forensic-vfs) converts its native
representation into these types via the ForensicFs
trait.
Structs§
- FsBlock
Range - A contiguous range of blocks.
- FsDeleted
Inode - Deleted inode information.
- FsDeleted
Node - A recovered deleted (or orphaned) node carrying the identity a consumer
needs to render and read it: a readable inode, the recovered name, the
parent inode (or
Nonefor an orphan), the metadata record id, and MACB times. UnlikeFsDeletedInode(bare inode + size), this is the rich surface backing in-place vs$Orphansplacement — the name is never fabricated (empty when the filesystem destroyed it on delete). - FsDir
Entry - Filesystem-agnostic directory entry.
- FsMetadata
- Filesystem-agnostic file metadata.
- FsRecovery
Result - Result of attempting to recover a deleted file.
- FsTimeline
Event - A timeline event.
- FsTimestamp
- Filesystem-agnostic timestamp.
- FsTransaction
- A journal transaction.
Enums§
- FsAllocation
- Name/metadata-layer allocation status of a recovered node.
Allocatednever appears here (a recovered node is unlinked by definition). - FsError
- Error type for
ForensicFsoperations. - FsEvent
Type - Type of filesystem event.
- FsFile
Type - Filesystem-agnostic file type.
Functions§
- not_
found - Helper to create a “not found” error.
- not_
supported - Helper to create a “not supported” error.
Type Aliases§
- FsResult
- Convenience alias.