It has just recently started using up our free Class B (download) transactions. I'm not really worried about this, I'll just increase the cap, but I am curious why rclone needs to download the files to set the mtime, and if this might be changed in a newer version. The error messages from rclone (once the cap is hit) say like "Failed to set modification time: Cannot download file, download bandwidth or transaction (Class B) cap exceeded".
Once we hit the cap, rclone starts spamming its output with errors; the first chunk are all rclonelinks but then it goes on to regular files after that.
Run the command 'rclone version' and share the full output of the command.
rclone v1.53.0
os/arch: linux/amd64
go version: go1.15
Which cloud storage system are you using? (eg Google Drive)
B2
The command you were trying to run (eg rclone copy /tmp remote:tmp)
2023/03/23 04:50:13 ERROR : rmt.rclonelink: Failed to set modification time: Cannot download file, download bandwidth or transaction (Class B) cap exceeded. See the Caps & Alerts page to increase your cap. (403 download_cap_exceeded)
2023/03/23 04:50:13 ERROR : printcap.rclonelink: Failed to set modification time: Cannot download file, download bandwidth or transaction (Class B) cap exceeded. See the Caps & Alerts page to increase your cap. (403 download_cap_exceeded)
2023/03/23 04:50:13 ERROR : shadow: Failed to set modification time: Cannot download file, download bandwidth or transaction (Class B) cap exceeded. See the Caps & Alerts page to increase your cap. (403 download_cap_exceeded)
2023/03/23 04:50:13 ERROR : pnm2ppa.conf: Failed to set modification time: Cannot download file, download bandwidth or transaction (Class B) cap exceeded. See the Caps & Alerts page to increase your cap. (403 download_cap_exceeded)
2023/03/23 04:50:13 ERROR : timezone: Failed to set modification time: Cannot download file, download bandwidth or transaction (Class B) cap exceeded. See the Caps & Alerts page to increase your cap. (403 download_cap_exceeded)
Yes, I know it is. And yet there's no reason for me to do the work to upgrade all of our systems if it still has the same behavior. Which is why I'm asking here.
Thanks for the suggestion. Yeah, it looks like the current version does the same, so I'll just need to raise the cap.
./rclone touch -vv b2:snucbackup/test
2023/03/24 13:23:12 DEBUG : rclone: Version "v1.62.2" starting with parameters ["./rclone" "touch" "-vv" "b2:snucbackup/test"]
2023/03/24 13:23:12 DEBUG : Creating backend with remote "b2:snucbackup/"
2023/03/24 13:23:12 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2023/03/24 13:23:12 Failed to create file system for "b2:snucbackup/": failed to authorize account: failed to authenticate: Transaction cap exceeded, see the Caps & Alerts page to increase your cap (403 transaction_cap_exceeded)
Yes sorry, I didn't bother to mention that. I'm not sure why it has to do that, either, since the same information appears to be returned by the various list methods. But ah well!