Expand description
Where a dataset physically lives, and what that implies about opening it.
The home screen’s job is to let someone decide what to open. Size and row count answer “what is this”; they say nothing about “what will happen when I press Enter”. A 2 GB file on tmpfs and a 2 GB file on a hotel-wifi NFS mount are the same row and a thousandfold different experience.
Everything here is derived from /proc/self/mountinfo, which is a local read of a
kernel-generated file: it cannot block on the filesystem it describes, which is
the whole reason it is safe to consult about a share that has stopped answering.
Structs§
Enums§
- Locality
- How a dataset is reached, in the terms that predict what opening it costs.
Constants§
- NETWORK_
FILESYSTEMS - Filesystems whose reads cross a network.
Functions§
- object_
scheme - The URL scheme of an object-store path, if it is one.