I am looking to ue rclone with Joplin. Joplin has built-in sync capabilities with webdav. Joplin can also sync to a local filesystem. Does anyone have any experience syncing Joplin to a local filesystem (rclone mount) and letting rclone do the syncing?
I tried it with the below mounting settings and it mainly appeared to work. The transfer stopped once with a Joplin API error (see the corresponding rclone error) however I was able to start it again and it finished successfully.
What is your rclone version (output from rclone version)
go version: go1.15.7
Which OS you are using and how many bits (eg Windows 7, 64 bit)
KDE Neon 5.21.4, 64bit
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
2021/05/11 13:33:31 ERROR : id.md: Failed to copy: Put "https://host/remote.php/dav/files/id": http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] after Request.Body was written; define Request.GetBody to avoid this error
2021/05/11 13:33:31 ERROR : id.md: vfs cache: failed to upload try #1, will retry in 10s: vfs cache: failed to transfer file from cache to remote: Put "https://host/remote.php/dav/files/id": http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] after Request.Body was written; define Request.GetBody to avoid this error
Joplin is a note taking app and it syncs small .md files for each note. Are my rclone mount settings appropriate for this usecase? Should I add or remove anything?
I am trying the same application with a similar config cross-platform on Android without vfs caching. I am seeing this error:
Date ERROR: file: WriteFileHandle: Can't open for write without O_TRUNC on existing fie without --vfs-cache-mode >- writes.
I would prefer not to use vfs caching if possible on Android due to resource constraints. Is this message telling me that I cannot write at all without using vfs caching? What is O_TRUNC in this context and how does it relate to vfs caching?
Thanks for the reply. Have you seen this error message before? Isn't filesystem access and operations handled at a lower level by the OS? Are you saying that rclone mount is not compatible with the way certain applications call OS resources to write files? Do you have any further information or are aware of documentation on the specifics so I can look for a solution?
If the file already exists and is a regular file and the
access mode allows writing (i.e., is O_RDWR or O_WRONLY)
it will be truncated to length 0. If the file is a FIFO
or terminal device file, the O_TRUNC flag is ignored.
Otherwise, the effect of O_TRUNC is unspecified.
In this case, yes the file does exits, it is a regular file and it has write permissions (0644). Is rclone here asking for O_TRUNC to be set on this file by the application in order to allow it to be written to?