Mhddfs meets the real environment

• No more segmentation faults which were introduced in 0.1.39. This was a main cause of 'Transport endpoint is not connected'
• Configure ulimits on startup to avoid the 'too many file descriptors' error on big production servers
• Require a proper (>= 2.9.4) version of FUSE in order to avoid "fuse internal error: node XXXXXX not found"

This repository will be discounted as soon as I'll receive a response from maintainer.

Here are some descriptions of that issue which I've found across the internets. If you've found this repository while searching a solution for that one then you're in a right place.

https://bugs.launchpad.net/ubuntu/+source/mhddfs/+bug/1429402

http://serverfault.com/questions/677352/mhddfs-randomly-breaks

http://stackoverflow.com/questions/24966676/transport-endpoint-is-not-connected

http://stackoverflow.com/questions/18006602/mhddfs-automount-failure-and-home-disconnection

CentOS

yum install git fuse fuse-devel glib2-devel gcc make libattr-devel
git clone https://github.com/vdudouyt/mhddfs-nosegfault/
make && cp mhddfs /usr/bin/

Debian

fakeroot dpkg-buildpackage

Docker

./build-docker
dpkg -i mhddfs_0.1.39+nosegfault2_amd64.deb
docker rmi <image-id>

It was reported that sometimes, mhddfs exits with the following error due to an internal bug in FUSE. It's highly suggested to use at least version 2.9.4 of FUSE in order to avoid that.

fuse internal error: node 2238037 not found

mhddfs#/pool/storage01,/pool/storage02,/pool/storage03,/pool/storage04 /storage fuse default_permissions,allow_other,mlimit=99 0 0