Hetzner Storage Box (CIFS)
-
Note that rclone mount is based on FUSE - https://rclone.org/commands/rclone_mount/ . So, symlinks etc won't work just like with s3fs.
@girish I think your info is a bit outdated, as their repo notes: https://github.com/s3fs-fuse/s3fs-fuse
Features
- large subset of POSIX including reading/writing files, directories, symlinks, mode, uid/gid, and extended attributes
-
@girish I think your info is a bit outdated, as their repo notes: https://github.com/s3fs-fuse/s3fs-fuse
Features
- large subset of POSIX including reading/writing files, directories, symlinks, mode, uid/gid, and extended attributes
-
I also had issues with CIFS in the past, switch to SSHFS and all has been well, except a couple of times on trying to restore a cloudron to another server. This just happened to me again yesterday where the restore the server from backup doesn't work (loading the backup config file) and I get the following error:
"failed to mount (inactive): read: Connection reset by peer"The same error is also reported in this post.
For it to work I had to connect to CIFS.
Weirdly now, in the restore server, the same storage box connects fine as SSHFS for volumes (and I didn't do anything, Cloudron just restored my Volume config).
So personally, I think there is a bug somewhere in Cloudron that prevents mounting SSHFS for backup on Server restore, because mounting as SSHFS works fine otherwise.
-
Cloudron really just uses the native linux cifs tooling, but by experience cifs with hetzner every now and then results in a bad mountpoint, where a remount is required. So far the investigations why and when that happens were unfortunately inconclusive. At least for me the SSHFS option is a lot more stable.
-
Cloudron really just uses the native linux cifs tooling, but by experience cifs with hetzner every now and then results in a bad mountpoint, where a remount is required. So far the investigations why and when that happens were unfortunately inconclusive. At least for me the SSHFS option is a lot more stable.
@nebulon said in Hetzner Storage Box (CIFS):
At least for me the SSHFS option is a lot more stable.
Out of interest, have you testing doing a restore too as per @avatar1024 example above?
-
Cloudron really just uses the native linux cifs tooling, but by experience cifs with hetzner every now and then results in a bad mountpoint, where a remount is required. So far the investigations why and when that happens were unfortunately inconclusive. At least for me the SSHFS option is a lot more stable.
@nebulon This has been my exact experience too, except when trying to restore a server where SSHFS fails and CIFS works (which arguably is pretty important
)And of course here someone also had mounting issues with SSHFS.
SSHFS seems too good and reliable to be abandoned on Cloudron just yet, especially as while not actively maintained for new features / some issues, it is still maintained for critical issues.
-
I am also using SSHFS everywhere when I can
-
-
@girish Will you keep "Hetzner Storage Box backend (based on rsync)" on your roadmap for 8.0?
-
G girish locked this topic on
