From 0bac344c8be407bda77f034a5a56fe7074a2eadf Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Mon, 1 Feb 2016 09:45:40 -0500 Subject: [PATCH] add information on fixing libfuse crashes --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 568de715..c5d5a7ff 100644 --- a/README.md +++ b/README.md @@ -338,6 +338,12 @@ Find extra tooling to help with managing `mergerfs` at: https://github.com/trape The gid cache uses fixed storage to simplify the design and be compatible with older systems which may not have C++11 compilers (as the original design required). There is enough storage for 256 users' supplemental groups. Each user is allowed upto 32 supplemental groups. Linux >= 2.6.3 allows upto 65535 groups per user but most other *nixs allow far less. NFS allowing only 16. The system does handle overflow gracefully. If the user has more than 32 supplemental groups only the first 32 will be used. If more than 256 users are using the system when an uncached user is found it will evict an existing user's cache at random. So long as there aren't more than 256 active users this should be fine. If either value is too low for your needs you will have to modify `gidcache.hpp` to increase the values. Note that doing so will increase the memory needed by each thread. +#### mergerfs / libfuse crashes + +If suddenly the mergerfs mount point disappears and `Transport endpoint is not connected` is returned when attempting to perform actions within the mount directory **and** the version of libfuse (use `mergerfs -v` to find the version) is older than `2.9.4` its likely due to a bug in libfuse. Affected versions of libfuse can be found in Debian Wheezy, Ubuntu Precise and others. + +In order to fix this please install newer versions of libfuse. If using a Debian based distro (Debian,Ubuntu,Mint) you can likely just install newer versions of [libfuse](https://packages.debian.org/unstable/libfuse2) and [fuse](https://packages.debian.org/unstable/fuse) from the repo of a newer release. + # FAQ *It's mentioned that there are some security issues with mhddfs. What are they? How does mergerfs address them?*