Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
files missing in synced folders on Linux, but not online or on Windows
I've been using Linux for a few months and the Linux version of Dropbox has been great. Recently, though, I wiped Linux, installed Windows, and then installed Linux again so I can dual-boot. I didn't...
Ok, all seems fine. Let's see the last steps. Check the current status using following:
dropbox status
Post the result and try again the following:
(IFS=$'\n'; for a in `find /mnt/sdc1/Dropbox -type d -print`; do if [[ "$a" =~ "/.dropbox" ]]; then echo "<empty>"; else cd $a; echo "In directory $a:"; dropbox filestatus; fi; done) | grep -vE "<empty>|up to date|\.dropbox|infinite" | grep -B 1 -vE "In directory .+:"
... to see if there is something wrong. Is there something received as a troublesome? 🤔 Hope if there is, the troubles to be less than before. Post such results, if there are some.
For the first one, it said "Up to date."
The second one took quite awhile. Eventually it produced "bash: cd: too many arguments."
sleepysloth wrote:
...The second one took quite awhile. Eventually it produced "bash: cd: too many arguments."
🤔 I confess, can't be sure what this means. If your folders/files count is big, the time for enumerating and evaluating every one is proportional, so it's normal to "took quite awhile". There is single "cd" command that in all calls takes single argument only. Can do you post the part where Eventually it produced "bash: cd: too many arguments."? 🧐
That's the only thing it displayed. I did it again and it still just displayed "bash: cd: too many arguments" and nothing else.
sleepysloth wrote:That's the only thing it displayed. I did it again and it still just displayed "bash: cd: too many arguments" and nothing else.
🤔Hm... The only chance such things to happen is using within file/folder name some unusual symbol, like semicolon, and some very old bash interpreter version. For actual versions this shouldn't be an issue, but... Let's try a bit patched variant of the command:
(IFS=$'\n'; for a in `find /mnt/sdc1/Dropbox -type d -print`; do if [[ "$a" =~ "/.dropbox" ]]; then echo "<empty>"; else echo "In directory $a:"; cd "$a"; dropbox filestatus; fi; done) 2>&1 | grep -vE "<empty>|up to date|\.dropbox|infinite" | grep -B 1 -vE "In directory .+:"
Now even for an old and buggy bash interpreter this should work (no chance the only argument be interpreted as multiple) and even when there is such or other error gonna be clear where exactly (in which directory) it happens. Let's see... 🧐
This just didn't produce anything for me. I tried it a couple times. It took awhile each time and then just displayed a blank command prompt.
sleepysloth wrote:This just didn't produce anything for me. ...
That's a good news generally. 🤷 If there is some result produced, it would be error and the result would direct where particular error comes up. In your case you haven't issues related to OS permission, for example, or similar able to prevent sync. I can't say anything more about your missing entries. Try trace what exactly you are syncing actually and where the discrepancy lies on exactly to fix it by hand. That's it.
