PLATFORM GUIDE / FIELD GUIDE 05

Linux Disk Browser

Connect filesystem-level capacity questions to directory-level evidence without hiding permission gaps.

Choose the level of investigation

A Linux disk browser workflow can combine a file manager, a graphical analyzer, and terminal observations. Start with the host, account, and path relevant to the workload. An authorized project review does not require scanning unrelated users’ directories. Describe mounts or execution environments when they affect which path you are actually observing.

Give filesystem and directory tools different jobs

The GNU df manual describes reporting filesystem space, while the GNU du manual documents directory and file usage measurements. Keep those labels distinct. The Lab article includes small read-only examples and explains how to record their scope.

Add a visual explanation when it helps

GNOME’s Disk Usage Analyzer offers tree and graphical views of folder sizes. Evaluate a visual tool with a known folder and pair the chart with readable paths. Preserve warnings and deliberately excluded locations in the written report, not just in the application window.

Do not make privilege escalation the default

When access is denied, first decide whether the location matters and whether you are authorized to inspect it. Ask an administrator for a scoped observation when appropriate. Route application data, retained logs, and build outputs to their responsible owners. A good investigation ends with understandable next actions, not a generic destructive command.

Questions worth asking

Should df and du show the same number?

They address different scopes and measurements. Compare their documented meanings and selected paths rather than assuming that subtracting them identifies removable data.

Do I need a terminal to use these guides?

No. The central method is a scoped observation with readable findings. A graphical tool can serve that purpose when it exposes the relevant path, measurement, and limitations.