MySQL over SLASH2 "does not work" #418
Description
The first requirement is that a Linux kernel version 4.0 or higher is needed due to a bug in fuse.ko that does not support the kernel aio interface correctly.
However, when running on such a newer kernel, attempting to initialize a MySQL database over SLASH2 actually triggers a segfault inside MySQL when a thread that is not prepared to handle realpath(3) failure tries to do so. The SLASH2 bug is that the realpath(3) should not be failing.
sshfs was tried, just to see if it is a problem with FUSE proper and it is also unable to handle MySQL. However, zfs-fuse was tried and succeeded with a problem, so it does not appear to be a problem with FUSE but SLASH2 in general.
Perhaps it is a LOOKUP/name timing/kernel caching issue. dircache was completely disabled in SLASH2 and the exact problem occurred, so I don't think the issue is there.