I did also try to limit tps with
--tpslimit=2 with mount command
Btw I upload big files without issue just random read is producing error at once, rate limit at once
Also it could be some change in dropbox policy or API limit also, I seen here few topic ppl complained, just strange i was told dropbox has less limit then google drive with API
I tried first to seek the file then to open with nano the big file 100GB one both produce rate limit almost at once, nano are opening for some 5-10s then produce r/w error and stop
It is supposed to be printing the error in here (error ) so it is impossible to tell what has gone wrong.
Can you try a run with -vv --dump headers - this will produce a lot of output - I'm only interested in the HTTP transaction (the REQUEST and RESPONSE) which causes the low level retry errors.
If you can't figure out which one that is then post the log from a bit before the first low level retry
Great log - thanks. We'd have needed --dump responses to see the error message (if any) but if you do that you'll also get any file data in the file which will be extremely messy.
It would be interesting to try that if you are feeling brave. The response gave Content-Type: text/plain; charset=utf-8 so we might get some text explanation rather than the JSON response that is usually returned from API calls.
The fact it didn't supply a JSON error probably means this is a bug in Dropbox as all API calls are supposed to return a JSON response.
Error in call to API function "files/download": Your app is not permitted to access this endpoint because it does not have the required scope 'files.content.read'. The owner of the app can enable the scope for the app using the Permissions tab on the App Console.
But as far I know I enabled all in API app, will check
Ok sorted had to recreate API app and enable files.content.read, I miss that check box last time