rclone: Incorrect sizes reported with rclone size
What is the problem you are having with rclone?
rclone size command is reporting an incorrect size in the Google Drive backend. It’s reporting nearly 1 TB more than what I got really.
This is the output of the command between 1.51 and 1.50.2 (the last version without issues). The rclone binary that’s in my path is 1.51 and the one in the folder I’m located is 1.50.2:
1.51 reports nearly 1 TB +. However, with the remote also mounted with 1.51, running a ncdu or du -sch command reports the correct size:
So it seems that there is a problem with the logic of the size of the backend introduced in 1.51, as 1.50 reported the sizes accurately.
What is your rclone version (output from rclone version)
I reproduced this in 1.51 and latest beta (rclone v1.51.0-054-gda5cbc19-beta). Older versions worked fine. 1.50.2 was the latest version to work without issues, so the issue was introduced in 1.51.
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Tests conducted in Windows 10 AMD64 and Raspberry Pi 3B+ (armhf). Tests with betas and older versions (until I found which one introduced the issue) were done in the Windows machine
Which cloud storage system are you using? (eg Google Drive)
Google Drive. It’s completely unknown to me if this issue is happening in other remotes.
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone size GoogleDriveBackend:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 24 (19 by maintainers)
Commits related to this issue
- dedupe: Stop dedupe deleting files with identical IDs #4013 Before this change if there were two files with the same name and the same ID in the same directory, dedupe would delete one of them but si... — committed to rclone/rclone by ncw 4 years ago
- dedupe: Stop dedupe deleting files with identical IDs #4013 Before this change if there were two files with the same name and the same ID in the same directory, dedupe would delete one of them but si... — committed to rclone/rclone by ncw 4 years ago
- drive: don't delete files with multiple parents to avoid data loss Rclone can't safely delete files with multiple parents without PATCHing the parents list. This can be done, but since multiple paren... — committed to rclone/rclone by ncw 4 years ago
- dedupe: Stop dedupe deleting files with identical IDs #4013 Before this change if there were two files with the same name and the same ID in the same directory, dedupe would delete one of them but si... — committed to dbramwell/rclone by ncw 4 years ago
- drive: don't delete files with multiple parents to avoid data loss Rclone can't safely delete files with multiple parents without PATCHing the parents list. This can be done, but since multiple paren... — committed to dbramwell/rclone by ncw 4 years ago
@ferferga Thank you, I have just upgraded from
1.52.1to1.52.2and it’s working correctly now.Those commits looks great, even more now than Drive is now using shortcuts. They will help a lot at easing the transition! Thank you very much @ncw!
@ncw Sure! Will do once I have everything copied over to my new Google Drive account. Should take 1-2 days with my connection.
Thanks!
Try with the
--disable ListRargument to rclone and see if the sizes match then.