Rclone v1.65.2 release

[ncw (Nick Craig-Wood)]

Rclone 1.65.2 has been released. Find it in the rclone downloads or use rclone selfupdate to upgrade.

This is a bug fix release which contains one very important bug fix for Azure Blob users.

• Azure Blob: IMPORTANT Fix data corruption bug (Nick Craig-Wood)

It was reported that rclone occasionally uploaded corrupted data to azure blob storage when using rclone sync/copy/move. This bug was introduced in v1.64.0 and fixed in v1.65.2. It seems to affect users using the --checksum flag on uploads the most. The corruptions are relatively rare even with the --checksum flag though. For a full write-up see issue #7590 which contains info on how to see if your data is affected.

Data corruption bugs are extremely rare in rclone - we go to huge efforts to prevent them, so we are very sorry to have to report this one. A big thank you also to the customer with a support contract for reporting this so we could fix it as soon as possible.

This release also fixes a long standing bug in the VFS/mount along with some doc fixes.

• Fix stale data when using --vfs-cache-mode full

Thank you to all the contributors to this release, those who contributed code or doc fixes or made issues or answered questions in the forum - your help is much appreciated!

If you’re working in the industry and you feel your company could benefit from a support contract please get in touch at sales@rclone.com or if you’re interested in advertising with us then please drop us a message to sponsorship@rclone.com.

Please consider donating or sponsoring to keep the project sustainable.

v1.65.2 - 2024-01-24

See commits

• Bug Fixes
  • build: bump GitHub - cloudflare/circl: CIRCL: Cloudflare Interoperable Reusable Cryptographic Library from 1.3.6 to 1.3.7 (dependabot)
  • docs updates (Nick Craig-Wood, kapitainsky, nielash, Tera, Harshit Budhraja)
• VFS
  • Fix stale data when using --vfs-cache-mode full (Nick Craig-Wood)
• Azure Blob
  • IMPORTANT Fix data corruption bug - see #7590 (Nick Craig-Wood)

[jcastill (Jose)]

Thanks for the release Nick. Seems https://downloads.rclone.org/version.txt is still not updated though shows 1.65.1

[ncw (Nick Craig-Wood)]

Oops, forgot to clear the cache - should be OK now.

[totov (tomas)]

Thanks for this update!

[random404]

@ncw

• • Fix stale data when using --vfs-cache-mode full (Nick Craig-Wood)

Can you be more clear on this? as someone that uses --vfs-cache a lot and still on rclone 1.62 I want to know if I should update

[kapitainsky]

vfs: fix stale data when using --vfs-cache-mode full

Cached webdav mount fingerprints get nuked on `ls`?

What is the problem you are having with rclone? We have a custom webdav backend that we're mounting with rclone, because rclone has awesome caching features that we don't have to implement ourselves, yay! We found at first that rclone was using only the file size as part of the cache fingerprint, which we resolved by upgrading to 1.65.1 and setting --webdav-vendor to rclone. This was enough to get the fingerprint to include both the file size and the last-modified header from the GET request …

[ncw (Nick Craig-Wood)]

@random404

as someone that uses --vfs-cache a lot and still on rclone 1.62 I want to know if I should update

If the objects in cloud storage are updated externally, then yes.

If you are running a mount and you never update objects except through the mount then it doesn't matter.

If the objects in cloud storage never get updated (only new ones added) then it doesn't matter.