trapexit/mergerfs

a featureful union filesystem

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 11th, 2026
Created on March 24th, 2014
Open Issues & Pull Requests: 29 (+0)
GitHub issues: Enabled
Number of forks: 224
Total Stargazers: 5,860 (+0)
Total Subscribers: 74 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.0 hours
Mean response time: 9.6 days
90th percentile: 29.4 hours
Tracked items: 90

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 5% of issues opened in the past year have been closed. Three people close 75% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 640 days
Stale 30+ days: 9
Stale 90+ days: 8

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • investigating (79)
  • bug (48)
  • feature (21)
  • question (11)
  • enhancement (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

mergerfs is a FUSE-based union filesystem that logically combines multiple filesystem paths into a single mount point.

The tool solves the problem of managing storage across numerous commodity devices by acting as a proxy layer that merges directory contents, deduplicates entries, and applies configurable policies to determine file placement and behavior. When files or directories are created, a policy engine selects which branch receives the new data. For operations that modify attributes or remove files, the tool can apply changes across all instances found. The underlying approach treats paths rather than block devices or mounts, allowing filesystems of any type and size to coexist without impacting one another if individual devices fail.

mergerfs suits users building storage systems from multiple drives, such as those running media servers or data hoarding setups. It works with read-only filesystems by ignoring them during file creation, supports hard links with copy-on-write semantics, and offers runtime configurability through extended attributes and POSIX ACLs. The tool provides near-native IO performance through passthrough support where available. Unlike overlay filesystems, mergerfs does not provide read-write overlays on read-only bases, does not support file whiteout, and does not include RAID-like parity or redundancy features. The README names mhddfs, unionfs, aufs, and DrivePool as comparable tools.

Maintainers respond to new issues and pull requests within hours. Work in the issue tracker centers on investigating problems, fixing bugs, and implementing features.