Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Dropbox keeps saying, Downloading 67 files...
Hi,
There's a similar topic, but nothing there works for me. Holding Space doesn't reveal any hidden buttons. I had files owned by root, but I changed the owner to my user (uid 1000) on the "s...
Solved it by temporarily moving the problem directory out of the Dropbox dir:
* on the target machine: stop the daemon and `mv ~/Dropbox/problem/dir ~`
* on the source machine: `mv ~/Dropbox/problem/dir ~` and wait until it syncs
* on the target machine: start the daemon and wait until it syncs
* `mv ~/dir ~/Dropbox/problem` on the source machine and wait until it syncs on both machines
* now ~/dir can be deleted on the target machine
This is in case you know that the target machine has no newer files.
P.S. As shows this discussion Dropbox desperately needs some kind of a log or a way to find out what's causing problems. The lack of it leads to unproductive discussions of a "what if you do this?" (guessing) kind.
Hannah
Dropbox Community Moderator
Dropbox Community ModeratorHey x-yuri, so you're seeing specific error messages about these directories? What do they show?
Is it possible that it's due to incompatible characters?
Hey Hannah. I'd really like it to give me some error messages. Where can I find them?
There are (1) a bunch of directories with the following icon:
but all the files inside these directories are green:
And there's (2) another directory with the blue icon. All the first level files and subdirectories there have these 2 icons:
The second level (or more) files and subdirectories have only the red icon.
Supposedly this directory was removed on the source notebook.
The characters used in the filenames (no spaces): a-z, A-Z, ., 0-9, _, @, -.
The maximum path length: 168 characters.
Solved it by temporarily moving the problem directory out of the Dropbox dir:
* on the target machine: stop the daemon and `mv ~/Dropbox/problem/dir ~`
* on the source machine: `mv ~/Dropbox/problem/dir ~` and wait until it syncs
* on the target machine: start the daemon and wait until it syncs
* `mv ~/dir ~/Dropbox/problem` on the source machine and wait until it syncs on both machines
* now ~/dir can be deleted on the target machine
This is in case you know that the target machine has no newer files.
P.S. As shows this discussion Dropbox desperately needs some kind of a log or a way to find out what's causing problems. The lack of it leads to unproductive discussions of a "what if you do this?" (guessing) kind.
