I downloaded the CLI and successfully with the first line. I would guess this is a one-time entry for this line?
Then, I entered the 2nd “sync” line and I got a message in the CMD window that said I needed the Odrive app running first, so I started it.
The Odrive app started and started automatically downloading files from all over the sync folders, so I stopped the automatic download.
Then, I ran the 2nd “sync” line again and nothing happened.
So, I turned automatic sync back on and then it started pulling the files from the intended folder, but it also started pulling many files from other folders. It definitely isn’t transferring one file at a time.
I do have some folders set with sync rules - from right-clicking on the folder and telling it to sync with recursive folders from then on.
If that’s the problem, I don’t know how to change those settings, once they are set.
I just set the auto download setting to “never download”, but dowloads from other folders keep restarting themselves.
Do I need to quit the odrive app after I change the auto download setting to “never download” and then restart it, and then run the command line sync command again?
There has no output after entering the 2nd sync line.
All that happens: a new command prompt appears with a blinking cursor.
Should there be output messages?
Hi @eric.koester,
I would expect some output. I would only expect no output if there were no .cloud files in the folder you are choosing to sync. Can you post the command you are running (or PM me if you don’t want to post here), so I can take a look?
Can you also send a diagnostic from the odrive menu?
For resetting sync rules on all folders, try this:
Right-click on the root “odrive” folder and select “Sync”
Hi @eric.koester,
I am waiting for the diagnostic to come in. It may take a while if you have a large local data repository.
I wanted to make sure that the files you see syncing are downloads and not uploads, though. odrive will always try to upload files that need to be uploaded. Folder sync rules won’t affect uploads and issuing a stop on a folder that is uploading files will just start again (the stop is only for downloads).
After resetting the sync rules, try restarting the desktop client and see if any files start downloading on their own again. Please also send another diagnostic since I haven’t seen this one come in yet…
I am mainly downloading files in recovery from the “Amazon Cloud Drive erasure of my local drive” event.
This is a MESS.
I am trying to prevent the big big files from downloading right now, because they never finish, just keep restarting. Since they never finish, they are just wasting bandwidth and delaying the smaller files that will download successfully.
Can you add an upload icon to be applied to files are are uploading and then users can see which are uploading and which are downloading?
As-is, there is only a magenta sync icon, and users can’t tell if it’s uploading or downloading.
There are about 1000 items in the waiting queue, which is probably why you are seeing things continuing to sync. A restart should clear this out so that the script can be the only one issuing the download requests, one at a time.
To make sure of this you can restart, turn off automatic sync, and then run the script.
Do you mean to restart only the odrive app or restart Windows 7 too?
I just restarted the odrive app, opened a cmd window, issued the sync command line and files from other folders started syncing again.
How can I see if they are uploads or downloads?
I just used the command lines you sent.
The other files from the other directories, are uploads, so all is working as expected.
I’ve been trying to rebuild my local directories with any backups I have here in the house.
Sometimes, Amazon Cloud and Odrive don’t see the files as the same on both ends, and so my locally reloaded file gets uploaded to Amazon Cloud.
It would be great if some of this command line status functionality could make it into the Windows application!
I noted that when I used it, I got a 1Mbit download stream of data.
When I opened a 2nd concurrent CMD window and entered another command line, I then saw about 2Mbit of total download stream.
It appears that each of these commands yeilds a 1Mbit download stream?
Hi @eric.koester,
I’ve found that Amazon Drive tends to behave this way for single-file downloads. I generally get a mediocre rate of download, but adding more concurrency multiplies it (to a point). You can run multiple commands to create concurrency. You may see some errors when one hits a files that is already being downloaded or was downloaded, but it should continue on.