duf vs dysk

duf vs dysk: compare their workflows, configuration choices, and practical tradeoffs.

Updated

short verdict

Both tools support customizable filesystem tables and JSON. Choose duf for its device and inode views, or dysk when CSV export fits the downstream workflow.

Start with mounted filesystems when you need to know which volume is full. Column choices, output format, and operating systems are more useful decision factors here than repository size.

this page is for

  • mounted-filesystem and inode checks
  • custom filesystem tables and CSV export
pick

duf

★ 15.4kGo
details

Use duf for mounted-filesystem tables with device filters, usage thresholds, and inode information.

best for

  • mounted-filesystem and inode checks

strengths

  • Filter local, network, fuse, loop, and other device types
  • Show block usage or inode information and export JSON
  • Runs on Linux, BSD, macOS, and Windows

weaknesses

  • A filesystem table identifies a full mount; finding the directories responsible requires a directory scan.
pick

dysk

★ 2.9k
details

Use dysk to choose filesystem columns and export the resulting data as JSON or CSV on Linux or macOS.

best for

  • custom filesystem tables and CSV export

strengths

  • Choose the filesystem attributes displayed as table columns
  • Filter filesystems and sort results by different columns
  • Export JSON or CSV for downstream processing

weaknesses

  • Its documented Linux and macOS target makes platform fit a consideration for a mixed operating-system fleet.

Key differences

  • Platform fit: duf covers Linux, BSD, macOS, and Windows; dysk targets Linux and macOS.
  • Exports: both provide JSON; dysk also provides CSV for tabular processing.
  • Filtering: duf offers device-type, filesystem-type, and mount-point filters; dysk combines filesystem criteria with sorting.
  • Table design: duf includes block and inode views with usage thresholds; dysk lets you select filesystem attributes as columns.

Choose duf when

  • Filter local, network, fuse, loop, and other device types
  • Show block usage or inode information and export JSON
  • Runs on Linux, BSD, macOS, and Windows

Choose dysk when

  • Choose the filesystem attributes displayed as table columns
  • Filter filesystems and sort results by different columns
  • Export JSON or CSV for downstream processing

FAQ

Will these tools tell me which directory is filling a disk?
They help identify the affected mounted filesystem by reporting usage and available space. Once you know the mount, scan its directories to locate the files responsible.
Which output should I use in an automated report?
Both export JSON for structured processing. dysk also exports CSV, which suits a downstream table or spreadsheet workflow.
How can duf reduce a noisy list of mounts?
Filter device types such as network, loop, fuse, or local devices, select filesystem types, or match mount points with wildcards. You can also choose which columns to display.

related