I'm not positive, but I think messages like these after all transfers complete are due to including the --create-empty-src-dirs
flag:
2022/05/31 10:42:03 INFO : 2022/05/31 10:42:03 - 1.107 TiB / 1.107 TiB, 100%, 9.092 KiB/s, ETA 0s
2022/05/31 10:42:03 DEBUG : home/user/5.20.11/NRD/backport/src/groovy/com/.svn/tmp/props: Making directory
2022/05/31 10:42:04 DEBUG : Temporary_Items/TeamRoom1_backup/Users/user/AppData/LocalLow/Sun/Java/Deployment/cache/6.0/58: Making directory
2022/05/31 10:42:06 DEBUG : home/user/New Laptop Movement/Documents/ABG/Rand.gov/branches/.svn/tmp/text-base: Making directory
2022/05/31 10:42:07 DEBUG : home/user/4.6.11 backup/nrd_public/grails-app/services/gov/.svn/props: Making directory
2022/05/31 10:42:07 DEBUG : home/user/New Laptop Movement/Documents/ABG/Coaches/branches/Milestone_Oct_06_2006/BRAC/javascript/.svn/props: Making directory
2022/05/31 10:42:08 INFO : 2022/05/31 10:42:08 - 1.107 TiB / 1.107 TiB, 100%, 9.092 KiB/s, ETA 0s
On large datasets (this is 1.25 TB), there can be a great many empty directories to create, but there's no information in the stats about how long this might take. The idea here is to include the count of directories that need to be created as part of the transfer count and decrement them as the directories are being created. Presumably that would lead to a non-zero ETA time as well.