Hi leeuniverse,
Thanks for reporting these from real day-to-day use. I went through each point against the code, and tested the rename one with the rclone version that ships with RcloneView.
1. Renamed folders being uploaded again
You found the right flag. rclone doesn’t keep a record of past transfers. On each run it compares the source and destination listings, so a renamed folder looks like a set of new files plus a set of files that no longer exist. Without --track-renames, it uploads the new ones and deletes the old ones.
The “may” in the docs is the catch. --track-renames is only used when certain conditions are met. When they aren’t, rclone writes a single error line to its log and goes ahead with the normal delete and re-upload. The Job still finishes as successful, so in RcloneView you can’t tell that the flag was skipped. In our tests it was skipped in two cases:
- In a Copy job (or Move). It only works with Sync.
- When the source and destination don’t share a checksum type, which is how it matches files by default. Your plain pCloud folder does share one with your local disk, so --track-renames on its own works there. The pCloud Vault doesn’t, because encrypted remotes have no checksums, and neither does a NAS added as an SMB remote.
What works for all three destinations is telling rclone to match files by name, size and modification time instead of by checksum. Put both flags in the Custom flags of a Sync job:
–track-renames --track-renames-strategy modtime,leaf
In a Job that’s Advanced Settings › Custom flags. In a Batch Job, it’s the Sync step’s Custom Flags › Additional flags.
We tested this by renaming a folder that had subfolders, with an encrypted remote as the destination. The files were moved on the remote and nothing was uploaded. With --track-renames alone, everything was uploaded again. rclone moves the files inside the renamed folder one by one on the server. If you turn on rclone logging with Log level set to INFO (Settings › General settings › Embedded Rclone, then Restart Rclone Now), the log shows a “Renamed from” line for each file. It treats a file with the same name, size and modification time as the same file, which is exactly what a folder rename leaves you with.
One thing to watch: in a Batch Sync step, don’t tick --delete-before together with it. rclone refuses to run that combination.
About adding it as a checkbox: a checkbox alone would still be skipped silently on the Vault, the NAS and Copy jobs, so we built a more complete version. It will be in the next release. Sync jobs get a “Detect renamed files” option. When the source and destination share no checksum, it switches to matching by modification time and name by itself, so it works for the Vault and the NAS too. If you add --track-renames to a Copy job, RcloneView now warns that it only works with Sync. In a Batch Sync step, it warns when --delete-before is ticked together with it. Until then, the Custom flags above do the same thing.
About asking the rclone developers: rclone already has this, as --track-renames, and it isn’t on by default. It uses extra memory, checksum matching has to read the renamed files to compare them, and it only works where the destination can move files on the server. So we think the better fix is on our side: making it easy to turn on, and showing you whether it worked.
2. --buffer-size 64M and the I/O errors
–buffer-size does reach rclone from Custom flags. It’s the memory rclone uses to read ahead from the source file, per transfer (16M by default), so with 2 transfers, 64M uses up to about 128 MB. It affects reading, not writing to the NAS, so on its own I wouldn’t expect it to stop write errors. Leaving it in does no harm, and for now Custom flags is the place for it.
To find the cause we need the error itself. Could you post:
- The exact error lines. If a step failed, the Batch window’s log shows its error. For full detail, turn on Settings › General settings › Embedded Rclone › Enable rclone Logging, click Restart Rclone Now, and run the transfer again. rclone.log is in your Documents folder by default.
- How the NAS is added in RcloneView: as an SMB remote, or as a drive letter or network path?
3. The Batch Job window
You’re right, and it’s worse than pointless. While a Batch Job runs, that window blocks the whole app, including the buttons in RcloneView’s own title bar. That’s why X (hide to the notification area) doesn’t respond and only the taskbar minimize works. The window can’t be closed until the batch finishes or you cancel it.
This is fixed for the next release. The window now has a “Run in background” button. It closes the window while the batch keeps running, and you can follow it in the Transfer window. When the batch finishes, RcloneView shows a notice. If you click Run on the same Batch Job while it is still running, the progress window opens again instead of starting a second run. We kept the window because it shows the step-by-step progress and log that the Transfer window doesn’t. Scheduled Batch Jobs already run without this window.
4. A date/time column in the Transfer window
The next release adds “Started at” and “Completed at” columns to the Transfer window. The finish time is now saved too, so both stay after you restart the app. Until then, the start time and each file’s completion time are only shown in the Job details window, which opens from the “See details” button on a Job’s completion notification.
Thanks again for running everything through RcloneView and telling us where it rubs.
Best regards,
RcloneView Team