Package Details: mergerfs 2.33.5-1

Git Clone URL: (read-only, click to copy)
Package Base: mergerfs
Description: Featureful union filesystem
Upstream URL:
Keywords: filesystem fuse
Licenses: custom:ISC
Submitter: pheerai
Maintainer: willemw
Last Packager: willemw
Votes: 32
Popularity: 0.057036
First Submitted: 2015-10-23 12:47 (UTC)
Last Updated: 2022-04-14 06:26 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

francoism90 commented on 2021-11-29 08:27 (UTC)

@willemw Thanks for the update. It's always a good idea to wait a week if serious bugs show up for fs-modules, so far it doesn't seem the case. :)

willemw commented on 2021-11-25 10:09 (UTC)

@francoism90: thanks for quickly flagging the package out-of-date. I follow the mergerfs releases with urlwatch, so it is unlikely I will miss a release.

I'll wait a week or so before updating the package, just in case there are some issues with the release.

willemw commented on 2021-11-20 13:06 (UTC)

I could add mergerfs-tools-git to be helpful and maybe I will. I've done it before for other packages (where both packages where -git packages). But the real/correct fix should come from mergerfs-tools-git.

Adding the conflict name here goes against the suggested guidelines: "..., you do not need to specify that conflicting package in your conflicts" (

Note: you can view the conflicts array as a list of provide names.

francoism90 commented on 2021-11-20 12:49 (UTC)

@willemw Please add mergerfs-tools-git instead, a stable/tagged release doesn't exists.

Adding conflicts is always useful to prevent overwriting/conflicts by the package manager.

willemw commented on 2021-11-20 11:13 (UTC)


Added provides name mergerfs-tools. Package mergerfs-tools-git still needs to be updated (see comment there).

mergerfs-git already provides and conflicts with (provide name) mergerfs. It is redundant for package mergerfs to conflict, the other way around, with mergerfs-git.

francoism90 commented on 2021-11-20 09:37 (UTC)

Could you please add mergerfs-tools-git as optdepends and add mergerfs-git as conflicts? :)

willemw commented on 2020-12-21 08:43 (UTC)

@trumee: it might be worth checking and/or reporting that upstream (

trumee commented on 2020-12-21 06:20 (UTC)

I was getting "Transport endpoint not connected" with kernel linux-lts-5.4.83-1 and mergerfs-2.32.1-1-x86_64.pkg.tar.xz.

Reverting back to 5.4.77-1-lts and mergerfs-2.31.0-1-x86_64.pkg.tar.xz resolved the issue for me.

willemw commented on 2020-03-25 00:08 (UTC)


My point was that it is not necessary to extend "arch" in order to build on ARM.

Even ArchLinuxARM themselves don't do it for their own repository packages. Not even for modified PKGBUILD files specific for ARM (

Sparticuz commented on 2020-03-24 23:57 (UTC)

@willemw I think what @cryzed is saying is that it builds just fine on arm, so adding arm would allow the package to be built on arm. In fact, looking at debians package, they have a bunch of different Arch's. ... Unless I'm missing something?

willemw commented on 2020-03-24 23:40 (UTC)


"any" will create a ...-any.pkg.tar.zst package file, which you can install on any platform. Used for installing script files, which are portable.

"x86_64" will create a ...-x86_64.pkg.tar.zst package file, which you can only install on a x86_64 platform. Used for compiled packages, which are only binary compatible with a specific platform.

willemw commented on 2020-03-24 23:19 (UTC)


I prefer not to extent the "arch" array. Most packages, that are compiled, don't do that (otherwise it would mean updating a lot of PKGBUILD files).

You can use "makepkg --ignorearch" (indirectly through an AUR helper) to build packages on other platforms. ArchLinuxARM even used to mention this in their Wiki.

Extending the "arch" array is, for example, useful for *-bin packages.

cryzed commented on 2020-03-24 23:02 (UTC)

@willemw thanks, but what about extending the arch array?

willemw commented on 2020-03-24 20:22 (UTC)

@cryzed: Thanks. Added fuse2.

cryzed commented on 2020-03-24 20:12 (UTC) (edited on 2020-03-24 20:13 (UTC) by cryzed)

You should define fuse2 as an optional dependency, it's needed to get mergerfs to work with /etc/fstab. Also I tested this successfully on a Raspberry Pi 4, the architecture armv7h can be added to the arch array.

moonman commented on 2019-06-29 00:50 (UTC)

@willemw I just did But kinda wanted to get some feedback here, maybe it is specific to my setup?

willemw commented on 2019-06-28 05:59 (UTC)

@moonman: Have you reported this upstream?

moonman commented on 2019-06-28 03:25 (UTC) (edited on 2019-06-28 03:25 (UTC) by moonman)

This is corrupting files for me.

Fine: source -> directly to pool member(bypassing mergerfs).

Corrupt: source -> mergerfs pool

Fine: source -> mhddfs pool (same hdd pool, mergerfs disabled, mhddfs enabled)

Tested with a 60GB video file and diff several times and different mount options.

willemw commented on 2019-05-17 10:27 (UTC)

@Raansu: Updated. You can use the "Flag package out-of-date" link on this page to request a version bump.

Raansu commented on 2019-05-17 10:07 (UTC)

Can you bump this to 2.26.2 please?

willemw commented on 2019-05-12 22:23 (UTC)

@mmozeiko: Removed fuse dependency.

mmozeiko commented on 2019-05-12 21:56 (UTC) (edited on 2019-05-12 21:56 (UTC) by mmozeiko)

From version 2.26 mergerfs does not depend on fuse anymore. See here:

Fully vendored libfuse

Please update Dependencies.

rspenc29 commented on 2018-12-08 14:38 (UTC)

I also had a broken mergerfs after the latest update. Installing fuse3 fixed it.

Sparticuz commented on 2018-12-04 14:55 (UTC)

I got the same error and it was fixed by installing fuse3

danch commented on 2018-12-03 18:42 (UTC) (edited on 2018-12-03 21:30 (UTC) by danch)

@willemw: Sorry it took me so long to respond. I didnt see your response until now. It looks like the issue might actually be with the fuse-common package. I am on fuse-common 3.3.0-1 as of a full system upgrade and it looks like this has come up before, as you can see here: I am thinking that fuse-common is wanting something out of fuse3. I could only get it to run after I installed that package. The error message was basically that it could not locate the library.

willemw commented on 2018-12-02 10:51 (UTC) (edited on 2018-12-02 13:11 (UTC) by willemw)


Cannot reproduce. Building mergerfs and mounting with mergerfs works without fuse3 being installed. Fuse3 should not be dependency.

What errors are you getting?

danch commented on 2018-12-01 22:04 (UTC)

I just did a full system update and mergerfs wouldnt start after that with version 2.25.1. Once I installed fuse3 everything worked again but without that I was getting errors where it says it couldn't find fuse3 packages. I am wondering if fuse3 is a dependency now and if that should be changed int he PKGBUILD.

willemw commented on 2018-11-06 21:13 (UTC) (edited on 2018-11-08 21:55 (UTC) by willemw)

@pheerai: I run a very basic sanity check with file images representing disks. For better testing, test scripts should be made available, see for example SnapRAID ("make check").

2.25.0 is out. It's a pre-release. See release notes. 2.24.2 is still marked as being the latest release.

pheerai commented on 2018-11-06 20:19 (UTC)

@willemw: Both. I would not detect any runtime issues, as well as any build time configuration problems that show up at runtime. I'm trying to at least test basic usability with my packages before updating. This is rather hard without any actual real-world use Case, IMHO.

So, no actual problems with the tool itself, but I'd rather not break anyone's disk setup as long as I can avoid it ;-)

willemw commented on 2018-11-06 20:13 (UTC)

@pheerai: what kind of FUSE issues? Only build issues or also run-time issues?

pheerai commented on 2018-11-06 19:22 (UTC)

As I have no use for this package, I disown it (I suspect that there might be quite some issues with FUSE-Stuff, and not using boils down to someone without any suitable setup basically poking around in cases of build mistakes).

Feel free to adopt, actually the PKGBUILD is quite straight forward.

rpodgorny commented on 2018-09-19 15:46 (UTC)

cosmetic side note: the pkgbuild in the repo seems to be executable ;-)

willemw commented on 2018-04-25 21:35 (UTC)

To build for another architecture you should use the "--ignorearch" makepkg option.

Raansu commented on 2018-04-25 19:43 (UTC)

Can you please add support for ARM devices? If I manually edit this for 'armv7h' it builds fine on my Raspberry Pi 3B+

pheerai commented on 2017-12-02 18:20 (UTC)

@willemw: The release / source issue should be fixed now, and the `|| exit` is removed (although this should do no harm). Thanks for this. As I'm creating the pkgbuild from a script that fills in a template, I see no use in pushing it with the placeholders. But thank you for the remark nonetheless.

willemw commented on 2017-12-02 15:18 (UTC)

The source URL should be changed: to include the mergerfs version number. See The "cd" command can also be improved: source=("$pkgver/mergerfs-$pkgver.tar.gz") cd "$srcdir/mergerfs-$pkgver"

willemw commented on 2017-11-28 12:41 (UTC)

"|| exit" is not necessary.

lockheed commented on 2016-08-08 21:02 (UTC)

Checksums don't match the source file.