How to get transferred / total size using rclone rc

Want to get the 749.606G / 15.520 TBytes shows as in the default output of rclone copy -v

2019/10/20 16:18:33 INFO  : 
Transferred:   	  749.606G / 15.520 TBytes, 5%, 782.435 MBytes/s, ETA 5h30m18s
Errors:                 0
Checks:              4649 / 4649, 100%
Transferred:          124 / 2929, 4%
Elapsed time:      16m21s
 *    Unknown.2011.720p.BluRay.DTS.x264-HiDt.mkv: transferring
 * Union.Pacific.1939.720…FLAC.2.0.x264-NCmt.mkv: transferring
 * Unleashed.2005.720p.Bl…ay.DD5.1.x264-NCmt.mkv: transferring
 * Unthinkable.2010.720p.…Ray.DD5.1.x264-EbP.mkv: transferring
 * Untraceable.2008.720p.BluRay.DTS.x264-PTP.mkv: transferring
 * Uomini_contro_1970_720…luRay_FLAC_x264-EA.mkv: transferring

When using rclone rc core/stats, it shows only how much has been transferred but no information of total size.

Have looked up document about rclone rc (the document is messed up since here possibly because Markdown problem) but there are too many available parameters (do not want to try it one by one :slight_smile:)

for the problem with the documentation, use the current version on GitHub; rc documentation

but it seems that you wouldn't find anything other...

This returns all available stats:

rclone rc core/stats

Thanks for this pretty doc.

cannot get total size using rclone rc sad. How dose the default output calculate it? Dose it run rclone size src: and rclone size dst: then calculate the gaps?

You could just check the code if you are comfortable reading that (go isn't the most cryptic of languages).
That is also right there on github, since you are looking for a very spesific function in the RC here it shouldn't be too hard to identify where in the code that is I imagine.

I don't think the queued transfers are in the stats at the moment :frowning:

What is in the stats could do with a bit of a revamp!

Can you please make a new issue on github and we can get them added in :slight_smile:

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