Getting error rclone on android using termux

i am getting error when syncing on android using termux.
i am downloading a keepass database from wasabi to my android phone.
the sync does work.
the upadted keepass database is downloaded and i am am to see the changes when using the keepass android app.

2019/12/31 19:59:05 DEBUG : rclone: Version "v1.50.2" starting with parameters ["rclone" "sync" "wasabieast2:en07/kdbx/rclone/backup/" "/storage/emulated/0/keepass/" "--log-level=DEBUG"]
2019/12/31 19:59:05 DEBUG : Using config file from "/data/data/com.termux/files/home/.config/rclone/rclone.conf"
2019/12/31 19:59:06 DEBUG : 01.kdbx: Sizes differ (src 98654 vs dst 98670)
2019/12/31 19:59:06 INFO : Local file system at /storage/emulated/0/keepass/: Waiting for checks to finish
2019/12/31 19:59:06 DEBUG : 01.key: Size and modification time the same (differ by 0s, within tolerance 1ns)
2019/12/31 19:59:06 DEBUG : 01.key: Unchanged skipping
2019/12/31 19:59:06 INFO : Local file system at /storage/emulated/0/keepass/: Waiting for transfers to finish
2019/12/31 19:59:06 DEBUG : preAllocate: got error on fallocate, trying combination 1/2: operation not supported
2019/12/31 19:59:06 DEBUG : preAllocate: got error on fallocate, trying combination 2/2: operation not supported
2019/12/31 19:59:06 DEBUG : 01.kdbx: MD5 = 6d566938fa767fa6ac44ff9bf99e446a OK
2019/12/31 19:59:06 INFO : 01.kdbx: Copied (replaced existing)
2019/12/31 19:59:06 INFO : Waiting for deletions to finish
2019/12/31 19:59:06 INFO :
Transferred: 96.342k / 96.342 kBytes, 100%, 595.176 kBytes/s, ETA 0s
Errors: 0
Checks: 2 / 2, 100%
Transferred: 1 / 1, 100%
Elapsed time: 100ms

2019/12/31 19:59:06 DEBUG : 7 go routines active
2019/12/31 19:59:06 DEBUG : rclone: Version "v1.50.2" finishing with parameters ["rclone" "sync" "wasabieast2:en07/kdbx/rclone/backup/" "/storage/emulated/0/keepass/" "--log-level=DEBUG"]

That looks like it worked fine except for these. Note they are DEBUG so you don't need to worry about them. Rclone is trying to use fallocate to improve performance, but it seems Android doesn't support it so it falls back to not using it.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.