Thank you so much for taking out your precious time to give a detailed reply to my question.
When I move a fileA, let's say from source/folderA to source/folderB, the copy command is keeping the fileA in the destination/folderA and creating a new fileA in destination/folderB (while the source and destination will be googledrive and raspberry pi in one command and in the next command the reverse)
So the two copy commands are not (at least in my case) making the two folders identical. Am I missing something?
(Also I just noticed that the second copy command is bringing back the fileA to source/folderA, so that the fileA is now in both the folders on source as well as destination)
I really appreciate the clear answer that you have given to my question
Apologies for the confusing sentence.
First copy command creates duplicate file in the destination. so the googledrive and localfolder are not identical.
The second copy command is again recreating the moved file by copying it from the localfolder to googledrive. Now the googledrive and localfolder are identical but with duplicate files.
Logically speaking this the expected behavior of the copy operation, but I was trying to understand the answer
"the copy command shouldn't be making duplicate files"
How safe is bisync? I mean is it as reliable as the native mirroring done by googledrive apps on windows?