Rclone about with dropbox reporte size incorrectly

What is the problem you are having with rclone?

rclone about used with dropbox advanced with 2 users, does not reporte size used correctly as in the web interface.

Run the command 'rclone version' and share the full output of the command.

rclone v1.65.0

  • os/version: alpine 3.18.4 (64 bit)
  • os/kernel: 5.4.0-81-generic (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.21.4
  • go/linking: static
  • go/tags: none

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


The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone about --full dropbox-account1:

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

type = dropbox
token = xxxxxx

A log from the command that you were trying to run with the -vv flag

2023/12/04 20:31:32 DEBUG : rclone: Version "v1.65.0" starting with parameters ["rclone" "about" "--full" "dropbox-account1:" "-vv"]
2023/12/04 20:31:32 DEBUG : Creating backend with remote "dropbox-account1:"
2023/12/04 20:31:32 DEBUG : Using config file from "/config/rclone/rclone.conf"
Total:   49478023249920
Used:    30872481118634
Free:    18605542131286
2023/12/04 20:31:33 DEBUG : 7 go routines active
2023/12/04 20:31:33 INFO  : Dropbox root '': Committing uploads - please wait...

rclone about remote: using with dropbox advanced and 2 users, it does not list the total size used or free globally as I believe the command should work. I even tried to register the remote of the 2 users and even adding the space used from the 2 accounts it does not report correctly. For example, in the web interface it lists account1 as having 24.81TB occupied, by rclone about account1: it shows 28,078 TiB used, even using the --full flag and transforming from bytes to TB does not appear correctly. The strange thing is that the total size works accordingly. I read the about and dropbox help pages and didn't find anything about this difference.

rclone does not do here anything massively creative but only displays formatted data provided by Dropbox API. It is possible that Dropbox API and web interface numbers are not in line... It is question to Dropbox why.

You can see Dropbox API response by adding --dump bodies flag to your rclone about command. It will be only one request and one response with latter containing all numbers available in bytes.

Thank you for responding. Can I help in any way? Opening a ticket on Dropbox and reporting that their API is incorrectly returning the data, is that it?

Or maybe their web is incorrect? I do not have dropbox account to test myself.

I believe that the web interface is correct, because if you add the values ​​in use from the web interface you will get the total value used and the free value will be subtracted from the total correctly. Considering the rclone values, they exceed the total available value.


rclone about --full dropbox: --log-level DEBUG --dump bodies
2023/12/06 14:20:37 DEBUG : rclone: Version "v1.65.0" starting with parameters ["rclone" "about" "--full" "dropbox:" "--log-level" "DEBUG" "--dump" "bodies"]
2023/12/06 14:20:37 DEBUG : Creating backend with remote "dropbox:"
2023/12/06 14:20:37 DEBUG : Using config file from "/config/rclone/rclone.conf"
2023/12/06 14:20:37 DEBUG : You have specified to dump information. Please be noted that the Accept-Encoding as shown may not be correct in the request and the response may not show Content-Encoding if the go standard libraries auto gzip encoding was in effect. In this case the body of the request will be gunzipped before showing it.
2023/12/06 14:20:37 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2023/12/06 14:20:37 DEBUG : HTTP REQUEST (req 0xc000209f00)
2023/12/06 14:20:37 DEBUG : POST /2/users/get_space_usage HTTP/1.1
Host: api.dropboxapi.com
User-Agent: rclone/v1.65.0
Content-Length: 0
Authorization: XXXX
Accept-Encoding: gzip

2023/12/06 14:20:37 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2023/12/06 14:20:38 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2023/12/06 14:20:38 DEBUG : HTTP RESPONSE (req 0xc000209f00)
2023/12/06 14:20:38 DEBUG : HTTP/2.0 200 OK
Accept-Encoding: identity,gzip
Cache-Control: no-cache
Content-Type: application/json
Date: Wed, 06 Dec 2023 14:20:37 GMT
Server: envoy
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Dropbox-Request-Id: 4e8245ef769940beb1798a1f4f1f0e4b
X-Dropbox-Response-Origin: far_remote
X-Frame-Options: SAMEORIGIN
X-Server-Response-Time: 252

{"used": 30870411807367, "allocation": {".tag": "team", "used": 47523695752081, "allocated": 49478023249920, "user_within_team_space_allocated": 0, "user_within_team_space_limit_type": {".tag": "off"}, "user_within_team_space_used_cached": 27283748923634}}
2023/12/06 14:20:38 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Total: 49478023249920
Used: 30870411807367
Free: 18607611442553
2023/12/06 14:20:38 DEBUG : 7 go routines active
2023/12/06 14:20:38 INFO : Dropbox root '': Committing uploads - please wait...


I'm sorry now that I saw the parameter to get the return of requests. Running here I saw that the user_within_team_space_used_cached part is the one that contains the correct space. calculating correctly matches what is in the web interface and adding up all the total space allocated correctly.

This appears to say that you have 30,870,411,807,367 used and 27,283,748,923,634 of that is from the team allocation. So I guess you have 3,586,662,883,733 stored in your personal allocation? Is that correct?

I checked here and the 27,283,748,923,634 are from the user folder. The 3,586,662,883,733 are more or less the files that are external to the folder and visible to both users.

Edit 1:

The 27,283,748,923,634 is the value that counts from the Total presented. These 3,586,662,883,733 are not counted in the free space count from what I understand.

Edit 2:

Looking at the numbers again, the global value of space used is where there is {.tag": "team", "used": 47523695752081 . This way the output would be the same as the output from the Dropbox Essentials account which matches correctly with the web interface of Dropbox.

Please give this a go. This uses the 47523695752081 figure as the used space which is what I think you are saying is correct.

v1.66.0-beta.7565.827b24617.fix-dropbox-about on branch fix-dropbox-about (uploaded in 15-30 mins)

Thank you very much, it's working perfect now. Both in the business and essentials accounts

Thanks for testing.

I've merged this to master now which means it will be in the latest beta in 15-30 minutes and released in v1.65.1

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