On Wed, 20 Sep 2017 00:49:06 -0700 Ben Gladstone <ben@gladstone.digital> wrote:
> I unfortunately haven't been able to identify a pattern, but every couple of > days mhddfs > crashes, giving me the message "The transport endpoint is not connected." > when I try to access > anything mounted by mhddfs. It's easy enough to fix, just "umount -l > <mountpoint> && mount <mountpoint>" > and it starts working again, but when it crashes it causes problems for any > programs currently > accessing that directory. > > When it crashes, this line appears in dmesg: > > mhddfs[561]: segfault at 0 ip 0000559e3eae159c sp 00007f2cded0da50 error 4 in > mhddfs[559e3eadc000+a000] > > I researched this issue and found a number of people talking about it online > but I didn't find a bug > report on the Debian bug tracker (I'm pretty sure it's not the same bug as > the segfault caused by updatedb). > > I believe I've found someone who's patched it already though, here's > his blog post about it: > http://nramkumar.org/tech/blog/2015/09/23/mhddfs-crash-with-ubuntu-14-04/. He > has posted the patch here: > https://github.com/ram-nat/mhddfs/commit/26d0f119eaa7e3ffaaf330bf29672e13471cb091. > > I'm trying out his precompiled binary to see if it fixes the issue for me as > well, but it hasn't been > long enough to know yet. Anyway, assuming it works, can we get this patch > merged into the main branch? FWIW I had tons of segfaults with mhddfs in the past (usually when browsing the mounted FS with Thunar file manager), then I've not used it for a period of time, then went back to using it recently, and have zero segfaults whatsoever now. I don't know what could be the change helping with this, in any case my versions are: Kernel 4.9.41 (Self-compiled) fuse 2.9.3-15+deb8u2 libc6:amd64 2.24-11+deb9u1 mhddfs 0.1.39+nmu1 One thing to check (some hunch), is any of your joined paths actually a symlink itself? -- With respect, Roman