Rclone log started fresh with this mount invocation. cache-dir=/Volumes/zvol01e_apfs/zRcloneCacheVFSĪs you can see both rclone and fuse set for debug logging.ġ4:30:47 PDT mount was halted on it's own by fuse - I did not kill the mount. Gdrive_team_zzBackups:/BorgBackup /mnt/GD Mount command contained in script (rclone_mount_VFS_only.sh) below: NOT using rclone backend cache for this particular test.Īs you can see below I'm basically using default values.

I also tried with OSXFuse 3.8.3 to see if the behavior was different. MacOS 10.14.5 Mojave (latest at moment of writing) We can cd into the directory and see nothing is there.

Gdrive_team_zzBackups:BorgBackup on /mnt/GD (osxfuse, nodev, nosuid, synchronous, mounted by xxx) 'OSError: Device not configured:'Īfter the error, the OS still shows the mount point I tried different caching strategies, but still have this same basic issue below, as illustrated with a VFS-cache:Īfter successfully writing some smaller files, and then a larger 501 MB file, osxfuse mount's contents dissappear after a few minutes, and borg is confused as to why everything has vaporized. Here's what I found using rclone with FUSE mounts when trying a borg backup. Some background: I can do this backup operation fairly reliably using Google Drive File Stream, so it would be great if we could get things reliable with rclone mount as well. The problem may exist without use of the cache, but I was not able to test for my particular application without use of the VFS cache. I ran into the following problem when using rclone FUSE mounts as a back-end for the borg backup program while using VFS-cache.

Os x fuse