HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
trapexit
mergerfs
C++2019–2025
trapexit / mergerfs

mergerfs

a featureful union filesystem

12Distinct people
15Mentions
0Explicit recommenders
6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

a featureful union filesystem

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year15 dated mentions

Observed mentions: 2019-11-19 13:30:47 UTC to 2025-12-01 02:55:46 UTC.

0123452019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC211
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC413
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC514

What Hacker News says

5 sources
Adding to the chorus of responses here: I did what this article suggested for a time, but found a purpose-built NAS was way nicer than repurposing an old gaming PC. Using an old gaming PC for a NAS is kind of like trying to use an old track car that you've taken out the interior, added in a roll cage, and welded the doors shut as your kid's first car. Like yeah it will totally work, and they can impress all of their friends as they cosplay as the Dukes of Hazzard, but it's really not optimal for the task at hand. I just upgraded my NAS setup to a Terramaster F4-425 Plus (running Debian) and it's great. The N150 CPU in it sips power, and the whole thing is tiny and easy to hide away in a media cabinet. One ultra-quiet Nocuta fan is all that's needed to keep it cool. It's so nice to use the right tool for the job. EDIT: I'd recommend all of
Read the rest
these guides / articles, I basically cherry-picked what I liked from all of them and ended up with something I'm really happy with: * https://perfectmediaserver.com * https://github.com/trapexit/mergerfs/blob/master/mkdocs/docs... * https://blog.muffn.io/posts/muffins-awesome-nas-stack/ * https://drfrankenstein.co.uk * https://trash-guides.info
In Don't throw away your old PC–it makes a better NAS than anything you can buy
I use mergerfs + snapraid on my HDDs for “cold” storage for the same reason: noise. Snapraid sync and scrub runs at 4am when I am not in the same room as the NAS. The drives stay spun down 99% of the time, because I also use a ZFS mirrored pool on SSDs for “hot” files, although Btrfs could also work if you're opposed to ZFS because it's out of tree. Basically using this idea, but with straight Debian instead of ProxMox: https://perfectmediaserver.com/05-advanced/combine-zfs-and-o... I also use mergerfs 'ff' (first found) create order, and put the SSDs first in the ordered fstab list of the mergerfs mount point. This gives me tiered storage: newly created files and reads hit the SSDs first. I use a mover script that runs nightly with the SnapRAID sync/scrub to keep space on the SSDs open. https://github.com/trapexit/mergerfs/blob/master/to
Read the rest
In Don't throw away your old PC–it makes a better NAS than anything you can buy
https://github.com/trapexit/mergerfs/blob/master/mkdocs/docs... I do this. One mergerfs mount with an ssd and three hdds made to look like one disk. Mergerfs is set to write to the ssd if it’s not full, and read from the ssd first. A chron job moves out the oldest files on the ssd once per night to the hdds (via a second mergerfs mount without the ssd) if the ssd is getting full. I have a fourth hdd that uses snap raid to protect the ssd and other hdds.
In Mini NASes marry NVMe to Intel's efficient chip

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.