fd95511091
Before this change, bisync needed to build a full listing for Path1, then a full listing for Path2, then compare them -- and each of those tasks needed to finish before the next one could start. In addition to being slow and inefficient, it also caused real problems if a file changed between the time bisync checked it on Path1 and the time it checked the corresponding file on Path2. This change solves these problems by listing both paths concurrently, using the same March infrastructure that check and sync use to traverse two directories in lock-step, optimized by Go's robust concurrency support. Listings should now be much faster, and any given path is now checked nearly-instantaneously on both sides, minimizing room for error. Further discussion: https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors
52 lines
2.1 KiB
Text
52 lines
2.1 KiB
Text
[36m(01) :[0m [34mtest rmdirs[0m
|
|
|
|
|
|
[36m(02) :[0m [34mtest initial bisync[0m
|
|
[36m(03) :[0m [34mbisync resync[0m
|
|
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
|
|
INFO : Copying unique Path2 files to Path1
|
|
INFO : Resynching Path1 to Path2
|
|
INFO : Resync updating listings
|
|
INFO : [32mBisync successful[0m
|
|
|
|
[36m(04) :[0m [34mtest 1. delete path1 subdir file[0m
|
|
[36m(05) :[0m [34mdelete-file {path1/}subdir/file20.txt[0m
|
|
|
|
[36m(06) :[0m [34mtest 2. run bisync without remove-empty-dirs[0m
|
|
[36m(07) :[0m [34mbisync[0m
|
|
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
|
|
INFO : Building Path1 and Path2 listings
|
|
INFO : Path1 checking for diffs
|
|
INFO : - [34mPath1[0m [35mFile was deleted[0m - [36msubdir/file20.txt[0m
|
|
INFO : Path1: 1 changes: 0 new, 0 newer, 0 older, 1 deleted
|
|
INFO : Path2 checking for diffs
|
|
INFO : Applying changes
|
|
INFO : - [34mPath2[0m [35mQueue delete[0m - [36m{path2/}subdir/file20.txt[0m
|
|
INFO : - [34mPath1[0m [35mDo queued copies to[0m - [36mPath2[0m
|
|
INFO : Updating listings
|
|
INFO : Validating listings for Path1 "{path1/}" vs Path2 "{path2/}"
|
|
INFO : [32mBisync successful[0m
|
|
|
|
[36m(08) :[0m [34mtest 3. confirm the subdir still exists on both paths[0m
|
|
[36m(09) :[0m [34mlist-dirs {path1/}[0m
|
|
subdir/
|
|
[36m(10) :[0m [34mlist-dirs {path2/}[0m
|
|
subdir/
|
|
|
|
[36m(11) :[0m [34mtest 4. run bisync with remove-empty-dirs[0m
|
|
[36m(12) :[0m [34mbisync remove-empty-dirs[0m
|
|
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
|
|
INFO : Building Path1 and Path2 listings
|
|
INFO : Path1 checking for diffs
|
|
INFO : Path2 checking for diffs
|
|
INFO : No changes found
|
|
INFO : Updating listings
|
|
INFO : Validating listings for Path1 "{path1/}" vs Path2 "{path2/}"
|
|
INFO : Removing empty directories
|
|
INFO : subdir: Removing directory
|
|
INFO : subdir: Removing directory
|
|
INFO : [32mBisync successful[0m
|
|
|
|
[36m(13) :[0m [34mtest 5. confirm the subdir has been removed on both paths[0m
|
|
[36m(14) :[0m [34mlist-dirs {path1/}[0m
|
|
[36m(15) :[0m [34mlist-dirs {path2/}[0m
|