Solved SSHFS Mount - 'Non Empty' mount option
After resizing my backup server to 1TB (Previously 500GB) I keep getting the below error when trying to remount the SSHFS share;
Failed to mount (inactive): fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option
@dylightful is it possible that on that mountpoint folder local files exist, which is causing the warning? Presumably the mountpoint will be a subfolder of
/mnt/. If you see files in the mountoint node, then check what those are and possible just remove them prior to mounting. (of course check if you need those then move them instead of removing)
@nebulon i was looking on the backup server..... cleared the /mnt/ on the main server.
Thanks for your help!
benborges last edited by benborges
@nebulon so wait...what about this use case : I have mounted my volumes just fine, have been using it as backup/video storage mounts for a while, then for some reason (after a reboot) my SSHFS mounts are all gone (red dots in the UI) so I detach those volumes from apps, remove them altogether, attempt at mounting the volume again from the UI and I get this exact same error.
My problem is that I cannot move the files, I cannot move 1TB of videos just to be able to mount the volume again.
Shouldn't the UI have the option to force the 'nonempty' mount option ?
robi last edited by
@benborges email support@ so they can take a look at why the mounts are failing.
alternatively look at the logs to find the mount messages or run the mount commands manually from the server via ssh.
benborges last edited by
@robi mounts work just fine from ssh/system
but the moment I use cloudron UI it's all borked
I'v sent an email to support, this is really strange because the volumes have been operating just fine for weeks.
@benborges I have a ticket in at the moment too regarding an SSHFS issue, may be a larger issue?
benborges last edited by
@dylightful Something definitely happened on Cloudron side and It's hurting me in full swing, I'm having a hard time to find the origin of this, it does not make any sense.
current operations at osintukraine.com are fully impacted, each of our telegram archive are now disconnected from their volume, already tried to clean start, new mounts, clean start, same problem.
Right now I'm trying to add a new sshfs volume, the target is empty, i'm still having this exact same error, I'm wondering if there isn't anything else going on here because nothing make sense.