Dataplicity LensLinux + macOS
GitHub
Suite / lens-disk
Storage

Find where storage pressure actually lives.

Inspect mounts, filesystems, capacity, inode use, block devices and deleted files that still occupy space.

Quick start

shell 
lens-disk
lens-disk --once
lens-disk --plain
lens-disk --filter /var
lens-disk --json

The interactive list opens with mounts first and block devices after them. Select a row and press Enter for the exact mount point, source, filesystem type, used and available bytes, capacity percentage and inode counts where available.

Reading the storage list

MountThe path applications write to, such as /, /var or a removable volume.
SourceThe backing device, logical volume, network share or platform-specific source.
FilesystemThe filesystem type reported by the operating system.
Used / availableByte counts for the mounted filesystem. Available space can differ from total minus used because of reservations and filesystem accounting.
CapacityThe reported percentage used. Lens health uses this value for filesystem-pressure findings.
InodesFile-entry consumption. A filesystem can run out of inodes while still showing free bytes.

Pseudo filesystems and development simulator mounts may appear in the inventory but are excluded from capacity-health checks where they do not represent ordinary persistent storage.

Common investigations

The root filesystem is nearly full

shell 
lens-disk --filter /
lens-logs --since "1 hour ago" --filter "No space left"

Confirm the affected mount rather than assuming every path shares the root filesystem. Check inode consumption and deleted-but-open files before removing data.

Space did not return after deleting a large file

On Linux, Lens reports deleted files that are still open by a process when the platform tools expose them. The file has no directory entry but its blocks remain allocated until the owning process closes the descriptor or exits. Use the listed PID and process context to decide whether a controlled service restart is appropriate.

Bytes are available but writes still fail

Open the mount detail and check inode use. Also verify that the path is on the mount you expected and inspect collection warnings for inaccessible or timed-out filesystem probes.

A removable or data volume disappeared

Search for its mount point, source or device name. If the block device is visible but no mount exists, continue with the operating system's native mount and device tools in the diagnostic shell.

Interaction

↑ ↓ / j kMove through mounts and devices
EnterInspect the selected item
EscReturn to the list
/Search mount, source, filesystem or device text
rRefresh storage data
!Open a diagnostic shell beside the view
qQuit

Mount capacity appears first; slower block-device and open-file probes continue in the background. The view remains navigable while those sections load.

Filters and output

shell 
# Human-readable snapshot for one area
lens-disk --plain --filter /var

# Full structured storage inventory
lens-disk --json --limit 0

--filter is a case-insensitive match across storage rows. --limit defaults to 1,000; use 0 for every available row. JSON keeps mounts, filesystems, block devices and deleted-open-file records in separate arrays and includes collection warnings.

Platform coverage

Linux

Lens reads mounted filesystems and inode usage, block-device inventory and deleted-open-file evidence using the facilities available on the system. Container, overlay and network filesystems are reported as the operating system presents them.

macOS

Lens reports APFS and other mounted volumes, simulator and removable mounts, capacity and inode data where available. Some low-level device or open-file relationships are less complete than on Linux and appear as unavailable rather than fabricated values.