Corrupted on transfer: MD5 hash differ in new VFS FULL

What is the problem you are having with rclone?

When I request to download new information to replace existing files via Emby, I get the message:
ERROR: HoltzFlix / Animes / Saint Seiya (1986) /fanart.jpg: corrupted on transfer: MD5 hash differ "d41d8cd98f00b204e9800998ecf8427e" vs "479d308d8cef2bf63fbf870197fadef9"

I have received these errors a few times generally when I send the metadata to be replaced by Emby, I believe it is something related to checksum, but I am not sure how it behaves with VFS FULL with dir-cache-time

What is your rclone version (output from rclone version)

rclone v1.53.1

  • os/arch: linux/amd64
  • go version: go1.15

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Ubuntu Server 18.04

Which cloud storage system are you using? (eg Google Drive)

Google Drive / Team Drive

The flags I'm using.

--log-level="${vfs_ll}"
--uid=1000 --gid=1000 --umask=002
--allow-other
--use-mmap
--poll-interval 1m
--drive-skip-gdocs
--cache-dir=/mnt/cache
--fast-list
--timeout=1h
--tpslimit=10
--user-agent="${uagent}"
--dir-cache-time 48h
--vfs-cache-poll-interval 1m
--vfs-cache-mode="${vfs_cm}"
--vfs-cache-max-age="${vfs_cma}"
--vfs-cache-max-size="${vfs_cms}"
--vfs-read-chunk-size="${vfs_rcs}"
--buffer-size="${vfs_bs}"

** rclone.env**

uagent=HoltzFlix
vfs_ll=NOTICE
vfs_bs=32M
vfs_rcs=64M
vfs_rcsl=2048M
vfs_cm=full
vfs_cma=48h
vfs_cms=100G

Can you share a debug log of the issue?

A debug log would be very useful.

When you say "I have received these errors a few times generally when I send the metadata to be replaced by Emby" has the file changed do you think?

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