Hey #linux#debian people: it’s occurring to me that #rclone might not actually be the best way to do what I’m doing. So: if you had two Debian servers on a vpn, both with 1 gig fiber links to the internet, in cities 100 km apart, how would you go about having shared filesystems between them? Right now I am using rclone mount with sftp. Is there a less janky way?

A deeply annoying discovery I made today: if you have an #rclone mount that needs to be restarted, any running #docker writing to that mount is now writing to your filesystem without warning. I get that if the mount is gone, of course it has to write to the local filesystem. But when the mount comes back, it continues writing to the local filesystem, but if you change into the mounted directory, ls will show the contents of the mount, not the contents of the local filesystem that docker is busy writing to, and you will have no idea what black hole your files are falling into, because /mnt/offsite shows it's mounted, your docker agrees that it's writing to /mnt/offsite, and yet the files are nowhere to be found when you go to /mnt/offsite! They only suddenly appear when you umount the directory.

I hate the way doing large #rclone syncs from slow cloud providers slows my entire #debian machine to a crawl, but because of the way iowait works and how rclone works, I don't think there's a good way around it? Has anyone found anything I missed?

What a nice discovery. I am an occasional #emacs user and latelly I have found out built-in tramp can be used with #rclone to work with files on rclone remotes.

I have just found out up to date version of #rclone can be used on non-rooted #android devices thanks to the #round-sync app. github.com/newhinton/Round-Syn… cc @IzzyOnDroid ✅