From ec97bb4d7fab153b1cdfaec2e5b654b80558bc33 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan-Philipp=20Re=C3=9Fler?= Date: Fri, 20 Feb 2026 05:05:03 +0100 Subject: [PATCH] docs: bisync - clarify flag interaction and minor changes The behavior of the --track-renames and --max-delete flags combination for bisync have confused me and some other users. So with this PR i added a paragraph to clarify this. --- docs/content/bisync.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/docs/content/bisync.md b/docs/content/bisync.md index c2e3a0012..d8d9ca658 100644 --- a/docs/content/bisync.md +++ b/docs/content/bisync.md @@ -477,9 +477,9 @@ their checksums would change from run to run (due to small variances in the internals of the generated export file.) Therefore, bisync automatically skips `--download-hash` for files with a size less than 0. -See also: [`Hasher`](https://rclone.org/hasher/) backend, -[`cryptcheck`](/commands/rclone_cryptcheck/) command, [`rclone check ---download`](/commands/rclone_check/) option, +See also: [`Hasher`](/hasher/) backend, +[`cryptcheck`](/commands/rclone_cryptcheck/) command, +[`rclone check --download`](/commands/rclone_check/) option, [`md5sum`](/commands/rclone_md5sum/) command ### --max-delete @@ -1120,8 +1120,8 @@ a mechanism to mark files as needing to be internally rechecked next time, for added safety. It should therefore no longer be necessary to sync only at quiet times -- however, note that an error can still occur if a file happens to change at the exact moment it's being read/written by bisync (same as would happen in -`rclone sync`.) (See also: [`--ignore-checksum`](https://rclone.org/docs/#ignore-checksum), -[`--local-no-check-updated`](https://rclone.org/local/#local-no-check-updated)) +`rclone sync`.) (See also: [`--ignore-checksum`](/docs/#ignore-checksum), +[`--local-no-check-updated`](/local/#local-no-check-updated)) ### Empty directories @@ -1161,6 +1161,11 @@ is to rename it to the same name on both sides. (As of `rclone v1.64`, a `--resync` is no longer required after doing so, as bisync will automatically detect that Path1 and Path2 are in agreement.) +Note that although the flag --track-renames ensures that renamed/moved files won't +be deleted and uploaded again, they are still counted as deleted files for purposes +of the --max-delete flag (as this check happens before the rename detection +operation). See [this issue](https://github.com/rclone/rclone/issues/8685). + ### `--fast-list` used by default Unlike most other rclone commands, bisync uses [`--fast-list`](/docs/#fast-list) @@ -1494,7 +1499,7 @@ and in most cases it's probably not what you want! To bisync Google Docs as URL shortcut links (in a manner similar to "Drive for Desktop"), use: `--drive-export-formats url` (or -[alternatives](https://rclone.org/drive/#exportformats:~:text=available%20Google%20Documents.-,Extension,macOS,-Standard%20options).) +[alternatives](/drive/#exportformats:~:text=available%20Google%20Documents.-,Extension,macOS,-Standard%20options).) Note that these link files cannot be edited on the non-drive side -- you will get errors if you try to sync an edited link file back to drive. They CAN be