‘rclone copy --max-transfer’ works beautifully in normal cases, in that it stops rclone after hitting the max.
However --max-transfer does not work with ‘rclone copy --drive-service-account-file’. For example, with a normal (non server-side) copy the progress tracker shows:
Transferred: 0.100 / 1.100 TBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0.200/ 1.100 TBytes, 0%, 0 Bytes/s, ETA -
and so on until it hits whatever amount you have put in --max-transfer=
But with --drive-service-account-file the progress tracker shows:
Transferred: 0 / 1.100 TBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1.000 TBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 0.900 TBytes, 0%, 0 Bytes/s, ETA -
and so on. If you hit the maximum allocation for a specific service account (e.g. 750GB with GDrive) then rclone stalls, sometimes for quite a while.
Is there any way to have rclone stop when using --drive-service-account-file when it stalls? I tried --timeout but it seems there is something that keeps the I/O timeout from being triggered.
All suggestions welcomed. The rclone command is a part of a script, so the intent is to let it stop/fail gracefully and then move on to the next line.
Thank you as always for the help.