Hmm, now that I see that odrive will automatically replace any missing .cloudf or .cloud files within the sync folder. How do I disable this? Leave odrive on, but have this feature off?
When I look at status I see:
odrive Make Cloud Storage THE WAY IT SHOULD BE.
isActivated: True hasSession: True
email: accountType: Google
syncEnabled: True version: prod 924
placeholderThreshold: neverDownload autoUnsyncThreshold: never
downloadThrottlingThreshold: unlimited uploadThrottlingThreshold: normal
autoTrashThreshold: never Mounts: 1
xlThreshold: never Backups: 0
Is there anyway I can adjust these settings? So that I can say, manually run an odrive sync “<list of .cloud files>” then move those files to googledrive, then delete those files, all the while having odrive turned on, but then NOT have odrive try and replace those .cloud files? My goal being to start deleting things after I’m 100% sure I have 100% of the .cloud files I want to sync. Because, well, obviously my ACD cloud isn’t ever going to change again, I’ve never uploading to ACD again… so barring anymore accidentally deletings of odrive, I won’t want this autosync’ing feature say, tomorrow, or the day after that.
I guess what I’m referring to is “unsync’ing”
you did write a script for this here:
I guess in theory I could sync a .cloud file then instantly unsync the file once it’s done being downloaded. For my usage case though it would be nice to simply disable creation of new .cloudf and .cloud files entirely, while at the same time still allowing manual sync commands of specific .cloud files I already have.
I’m assuming if I say, unsync’d a directory full of .cloud files and then tried to manually sync one of those files it would give me an error right? Or am I misunderstanding the unsync command? and it already does exactly what I wanted? Or even the opposite of what I want (heh)?
I even read this:
But I’m still not sure. Is it possible to have a sync’d file in an unsync’d directory? or is it possible to have a sync’d directory with both unsync’d and sync’d files inside? (clearly yes) but what’s the best way for me to achieve this.
The part that scares me about unsync is that in the -help for unsync I see this:
"
–force force unsync a file or a folder - permanently deleting any
changes or files that have not been uploaded.
"
This seems to imply that if I sync a .cloud file to generate a download of the real file. Then unsync the real file. It will instantly delete the real file? When what I want it to do is block attempts to download future placeholders for that file. Given how scary the wording on --force is though I think I might be afraid to attempt unsync’ing a file.
This might mean I end up having to move folders to googledrive in entire lots, and once an entire folder is safely on googledrive I could then unsync the folder in odrive, this might delete the folder but it should also block redownloading the .cloudf file? right? or will I need to build my own list of .cloudf files I want to ignore in future find . -name “*.cloudf” sync commands?
Does the unsync command simply turn healthy files back into placeholder files? Is there no way to block infinite regeneration of placeholder files? (Short of deleting files off of ACD; speaking of which, is there anyway to make odrive delete files off of ACD? Since I’m migrating the copy of the files I care about is the local copy, not the remote copy, the way sync and unsync are worded seems to indicate the main usage of odrive is when the remote is the main copy and the local copy is unimportant).
Or am I still misunderstanding sync states? and once everything is fully refreshed, can I simply sync a .cloud file, move it to googledrive, delete it, and it won’t magically reappear as a .cloud file unless I run a refresh command?
Assuming everything I said above is gibberish, I guess I can just run
find . -name “*.cloud” -mtime -1 -exec python “$HOME/.odrive-agent/bin/odrive.py” sync {} ;
I can simply let odrive functionally normally, and just ignore everything it’s done recently, leaving a bunch of files and placeholder creation that I don’t want done, and well, just ignoring it and leaving it be. This solution is extremely easy and simple, but I don’t like it, it’s messy, and doesn’t fill me with confidence.