trapexit
Members
-
Joined
-
Last visited
Everything posted by trapexit
-
mergerfs hasn't changed in any significant way in 5+ months. In fact I only just released a new version a 2 weeks ago and had no default behavior changes from the release prior.
-
Well, this is where I'm a bit confused. The "broken build" was literally a broken build. It didn't spit out a binary. So it couldn't have lead to any runtime mergerfs issues but there seems to be claims of that.
-
I'm not fully following all the issues here so just going to make a few statements: 1) The container image I provided is just a builder. It just grabs the source and builds a static binary. I didn't realize people were using it as a dependency for other things. I made it to make it easier to build a static binary manually. The issue was that it was pulling from the master branch and I checked in something that broke building on Alpine (which I use for static building in the image). That image now will build the latest tagged version which right now is 2.29.0. 2) Not sure I follow the situations where people said things blocked. There are no known bugs in mergerfs though there are some kernel bugs in recent kernel versions. Not sure what version UnRAID uses or if it is impacted. I'd need more info / reproducible example to comment further. 3) hardlinks. If the software is trying to link across devices... it'll fail. If you have a path preserving policy and a link would result in cross devices... it'll fail. Only if link/create are not path preserving will it always succeed (since it clones the path on the same branch). Even if the underlying device is being linked to/from mergerfs it will fail. *Any* cross mount link or rename will fail.
-
The image was just for building the master branch. No one ever mentioned wanting to us it as a dependency to something else. It just builds a static binary in an alpine container. I've updated to build with the latest tag rather than master and you can override it with the envvar TAG. If you want stability you should probably pick a specific version and not just get whatever happens to be latest.
