I’m using odrive to sync Box.com to a PC and I just noticed strange things happen this morning.
For example, it updated from Box to PC:
Beeman Investment Portfolio/01. Opportunities Pipeline/2022/Pipelines 301-400/2022-354 - TW Beeman NAV Loan/03. DD - Beeman Tachs/01. Initial DD to point of closing/4. 02-21-23 - unfunded amount & cash flow forecast/02-15-23 - GS request for unfunded amount.pdf
Less than 1 minute later, it uploads from PC to Box:
Beeman Investment Portfolio/01. Opportunities Pipeline/2022/Pipelines 301-400/2022-354 - TW Beeman NAV Loan/03. DD - Beeman Tachs/4. 02-21-23 - unfunded amount & cash flow forecast/02-15-23 - GS request for unfunded amount.pdf
By comparing the path, you can see the PDF file was copied from original folder to a different folder then got uploaded.
This is just one example. Lots of files were uploaded like this today, all went to different folders and created duplicates on Box. The PC in the sync pair is not used by anyone. It sits in a locked IT room. So, no one touched it. I am using odrive for one-way sync purpose. But even though this feature had been requested long before, you haven’t added it to the program (Why?). I don’t know how long it’s been doing this kind of copying/uploading, maybe for months, now that I’m looking at the sync log. If there’s one-way sync option, it would have prevented this from happening.
On another note:
Why for the Successful Download items, it uses "" for folder path, while for Successful Upload and Success Update items, it uses “/”?
odrive won’t copy files around, on its own, so there must be something else at work here. For example, maybe there is a local symlink to 03. DD - Beeman Tachs/4. 02-21-23 - unfunded amount & cash flow forecast inside of 01. Initial DD to point of closing, or vice-versa?
There is a way to prevent file updates in the client, using an advanced configuration setting, but not new file uploads. Have you looked into changing the permissions for the Box user to have read-only permissions, so that it is not allowed to write to Box?
I think this is just a case where the path is not being normalized for the OS for uploads. We can look into it, but it is purely cosmetic and doesn’t indicate any functional difference.
The way I use odrive is just to backup whatever files on Box.com to a local computer. As I mentioned, this PC computer is not used by any office users. I also don’t log on to it on daily basis. No one creates symlinks on the computer.
I occasionally log in via Remote Desktop and find a dialogue box asking for permission to delete files that were deleted from Box, and I simply click to confirm. Sometimes there is another warning window on top of that dialogue box – I don’t remember what it says. I just dismissed both windows and let it sync. Maybe that’s the cause for yesterday’s incident.
Is there a way for the software to bypass deletion confirmation windows automatically, instead of me doing it manually? Sometime there will be a week or two that goes by before I log into that PC again. I think it might cause problem when the deletion occurs but odrive still keeps syncing all the folders.
I took a look, and it looks like there was a flurry of activity when upload occurred, with downloads, moves, and deletes of several folders. odrive detected that one of the folders being removed had unsynced items in it, so it aborted the delete and re-uploaded the contents. The client behaves this way because it always errs on the side of preserving data, rather than deleting it.
I can’t tell why it believed there were unsynced local items, but it may have had something to do with an error that Windows came back with when trying to move a folder to the recycle bin, so what you said above makes sense.
Here is what I recommend for next steps:
You are running an older version of the client, which generally isn’t a problem, but for your particular use case there have been some changes that I think will help. So you should update to the latest version.
Change the advanced configuration option osTrashOverride: Advanced client options
It should be set to at least 1 to skip the recycle bin when there is an error. You may want to set it to 2, though, to always skip the recycle bin when there is a remote to local delete.