Hi, I’ve mounted my root odrive folder on linux, and must have done a sync --recursive at some point.
If I locally create a few test files, then refresh the folder they are in, then they are propagated to oneDrive. If I delete them in oneDrive, they do disappear from local. But if I delete them locally, they don’t disappear in oneDrive. Is this expected behavior on a free account?
test1.txt - delete locally - remains in oneDrive
test2.txt - delete in oneDrive - disappears from local
Hi @kelsangrinzin,
If you use the emptytrash command, it will empty the odrive trash.
The odrive trash is a safety feature to prevent unintended local deletes from being synced to the remote storage. Here is the documentation about it, which is geared towards the GUI desktop client, but the idea is the same:
Thank you, Tony,
The file has not gone to trash, it is still sitting in the original folder where it was created. Deleting on oneDrive had no effect on the client.
Remote to local deletes were seen to be working (delete something on OneDrive and it is deleted on local after a refresh).
Local to remote deletes were not seen to be working (delete something on local and it is not deleted in OneDrive after a refresh).
2 is expected due to the odrive trash. If you delete an item locally, odrive will see that the file is gone and queue that delete in the “odrive trash”. It will stayed queued in the odrive trash until you empty the trash or restore it. Emptying it will send the delete to OneDrive. Restoring it will put the file back as a placeholder file on the local.
You can see what is in the odrive trash by using the “status --trash” command.
Is what you are seeing now explained by 2, or are you seeing something else?