Search results

Putting aside all performance considerations, things seem to work for us and sshfs. Need to note that this storage is only used for a sync job. Is "missing O_TMPFILE" something that can break the backups in any way?

Adding fuse mount options sync_readdir,dir_cache=no,no_readahead,sshfs_sync,max_conns=1 solves that last issue. Did not investigate which one(s) of them. Sshfs shorage over the internet is slow, but seems good enough when having a decent ping time, high deduplication factor, backups size...

Seems like it is possible to get sshfs working but with some caveats: even if complete sshfs mount contents are owned by backup:backup, it somehow still wants to change some ownerships when initializing a datastore and EACCES: Permission denied is thrown (it turns out that sshfs does not...

A helpful thread. There is the same issue on bullseye, downgrading from bullseye 0.8.36 version to 0.8.35+pve1 seems to help (but 0.8.35+pve1 version is no longer available in proxmox bullseye no subscription repo): wget...