extfuse VS google-drive-ocamlfuse

FUSE does not work well with a large number of small files (due to high metadata ops such as inode/dentry lookups).

ExtFUSE (optimized FUSE with eBPF) [1] can offer you a high performance. It caches metadata in the kernel to avoid lookups in user space.

1. https://github.com/extfuse/extfuse

I fixed the problem, it was due to the incorrect setup of the google drive. I followed this guide to set everything up from scratch and create the folder directly in Linux instead of constantly accessing the apparently "encrypted" cloud. If anyone ever runs into the same problem, I really hope this thread is helpful :D

You might be able to use something like https://github.com/astrada/google-drive-ocamlfuse

Its a little hacky, but google drive with mounted ocaml-fuse kinda does-ish this... though git/GitHub does the trick, too.

There are fuse drivers like https://github.com/astrada/google-drive-ocamlfuse but I pretty darned sure it's using exactly the same transport protocol as Google's own app.

you might be able to load a drive with locally with google-drive-ocamlfuse but you wouldn't get access to google drives proprietary files (google doc, sheet, slide, etc)

There's always the excellent unofficial google-drive-ocamlfuse which uses FUSE to mount Google drive to a local directory.

https://github.com/astrada/google-drive-ocamlfuse

Agree with previous comment, dejadup is a good option for local backups, but there isnt a really good backup cloud tool in linux enviroment: https://github.com/vitalif/grive2, https://github.com/astrada/google-drive-ocamlfuse, etc.