(just test around), in android (via using adb root in termux), rclone mount with --vfs-cache-mode full without specifying the --cache-dir, an edit to .docx file in the mounted path might make the file corrupt (using google docs).
alternatively, it was because of google docs app (idk, just sharing what i found)
android screen record, if it useful
Run the command 'rclone version' and share the full output of the command.
Which cloud storage system are you using? (eg Google Drive)
[secure-rclone-android]
type = crypt
remote = /storage/redacted/DATA/android/redacted/secure-rclone
password = XXX
password2 = XXX
### Double check the config for sensitive info before posting publicly
The command you were trying to run (eg rclone copy /tmp remote:tmp)
2026/mm/dd hh:39:50 ERROR : Failed to create vfs cache - disabling: failed to create data cache directory: mkdir /.cache: read-only file system
2026/mm/dd hh:40:41 NOTICE: Encrypted drive 'remote:': --checksum is in use but the source and destination have no hashes in common; falling back to --size-only
2026/mm/dd hh:55:56 ERROR : test/test-docx-with-gdocs.docx: WriteFileHandle.Write: error: Bad file descriptor
editing .docx file is work with correct --cache-dir
i mean maybe it better if the mount become read only when user use --vfs-cache-mode full but forgot about `--cache-dircan be in not writeable file system
i use vfs after asking llm about i can't edit .docx but can edit .txt. it forgot to warn me about the cache dir, maybe because my prompt... (please be concise) lol
btw, is it safe doing mount in android? i like it because it safe storage spaces
thx @LeoW i will look into it. maybe i'll less hesritate if the github readme page mentioning "featured in" some external sites, best if it in official rclone page or forum
anyway, i hope i don't wasted people time eyeing my rclone log, so here is my attempt to summary the log when the file write happened (comparison between editing txt vs. docx in rclone mount not using vfs)
anyone can simply post software into the related section and it is accepted as is.
no verifcation, no validation.
as a forum moderator, and speaking for myself, i have complained against this.
i would not allow the related section, nor allow anybody to simply post software based on a unverified claim to be related to rclone.
recently, there are many so called related software mentioned on this site.
no idea who wrote the software, what their intentions are today, what there intention might be in the future, no idea how the github repository is protected and so on.
