How to analyze remote Linux disk usage over SSH
Analyze remote Linux disk usage from a Mac with a read-only workflow for filesystem capacity, directory size, large files, growth, and cleanup review.
Direct answer
Start with the full filesystem, narrow to one mount and directory scope, then rank directories and files before comparing a later snapshot. Keep discovery read-only: identify the owner and retention policy before considering any cleanup command.
When this guide applies
- A production server reports low free space and you need a safe first pass.
- You manage several Linux distributions from one Mac.
- You want a visual directory map without installing a server-side agent.
Step-by-step review
Verify the SSH destination
Use an existing SSH alias or an explicit user and host. Review host-key prompts instead of bypassing them.
Read filesystem capacity
Use the mounted-filesystem view to find the constrained mount; capacity and directory totals answer different questions.
Choose one scan scope
Start at the affected mount or service data directory and keep filesystem boundaries explicit.
Rank evidence
Review the largest directories, largest files, classification hints, permission gaps, and scan completeness.
Save a comparable baseline
Keep the complete local snapshot and repeat the identical host and scope later to measure growth.
Technical context
SSH is the transport, not the measurement
OpenSSH can execute a command on the remote host. The accuracy of a storage view still depends on the selected scanner, server permissions, filesystem semantics, and whether the scan completed.
Capacity and hierarchy must stay separate
Filesystem capacity comes from df-style statistics. Directory and file totals come from walking visible paths; neither should be silently substituted for the other.
Portable support requires capability detection
GNU find can provide structured metadata efficiently; Python 3 is a useful fallback; BusyBox builds vary, so each required option must be detected instead of assumed.
A visual map is evidence, not deletion permission
Large size, a familiar cache path, or an old modification time does not establish that an item is disposable.
Risks and actions to avoid
Incomplete scans undercount
Unreadable paths, disappearing files, transport interruption, or unsupported tools can leave gaps. Do not use an incomplete scan as a growth baseline.
Mount boundaries change totals
Crossing into another mounted filesystem can mix capacity domains; staying on one filesystem can intentionally omit mounted children.
Remote login has normal side effects
The app sends read-only probes, but SSH and server audit systems may still record the login and command execution.
What the Omuuz product can—and cannot—do
What it can do
SSH Disk Visualizer can use detected Linux tools over OpenSSH to build a local metadata map, rank large items, classify likely space consumers, and compare matching complete snapshots.
What it cannot do
It cannot guarantee access to every path, infer that a file is safe to delete, read file contents, install an agent, elevate with sudo, or change the remote server.
Product evidence
