I've got a self-written FUSE file system I mount on my NFS server on mountpoint /export/example/mount
. Then I export a parent directory of the FUSE via NFS. The /etc/exports
contains the options nohide,crossmnt,subtree_check,ro,no_root_squash
and allows free access to everyone:
/export/example *(nohide,crossmnt,subtree_check,ro,no_root_squash)
I can mount this export on my NFS client and access it. As soon as I access the FUSE within the NFS my client hangs until I umount
the NFS (and I need to use option -f
to accomplish that).
I've tried mounting the FUSE as my working user and as root. The results are the same.
The server is running a Ubuntu 12.04, the client a SuSE 9.3. The FUSE is written in Python and works locally without any trouble. Only the export via NFS fails. I have no security restrictions as all this is on a private network with only trusted users.
Does anybody have an idea what could cause my trouble or (even better) how to solve the issue?
I've thought about replacing the NFS with SSHFS to work around the problem, but that does not work as the client system is too old to support SSHFS (as it is based on FUSE, and FUSE isn't supported).
allow_other
option to sshfs mount?crossmnt
? And does the fuse-side (the s3fs) allow being used by other users (there's a mount option for this, too). Don't forget that fuse is user-space (meant to be used by one single user) while nfs is multi-user.