Linux – the potential for a FUSE mount to destabilize a Linux server

fuselinuxsshfs

I'm a sysadmin for a multi-user server, where students in our department have shell accounts. One of our users has requested that we install sshfs on it. I'm debating whether it would be wise to install sshfs as suggested.

My main concern is whether a FUSE mount could make our server less reliable. In my experience, bad things can happen to servers when an NFS server suddenly becomes unavailable — the load average shoots up, and you might not be able to unmount it cleanly, to the point where a hard reboot might be necessary. If a FUSE-mounted server suddenly disappears, how hard might it be to clean up the mess? Are there any other likely catastrophes or gotchas I should consider?

At least with NFS, only root can mount, and we can choose to mount NFS servers that we consider to be reasonably reliable.

Let's assume that our users have no hostile intentions, but might do stupid things accidentally. Also, I'm not really worried about the contents of the filesystems they might mount, since our users already have shell access and can copy anything they want to their home directory.

Best Answer

I have used FUSE with both sshfs and HDFS. sshfs seems to be very reliable, I've not seen a panic or hard crash at all. HDFS otoh has caused numerous crashes. This was investigated tuned, so long as we don't see heavy usage of hdfs everything is stable.

I've seen sshfs's host systems disappear with no ill effects. HDFS caused all kinds of problems. This leaves me with the impression that sshfs is quite stable.

I would suggest testing lots of I/O and see how sshfs handles it, I expect it would handle it like a champ.