Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Dropbox is stuck syncing after an update, what can I do?
I have the "Dropbox Plus" subscription and I run the client on 4 computers.
Yesterday (Monday, 13-Jan-2020) I signed onto my desktop (which is always on) and has a full local sync of my dropbox...
Okay, so i decided i'd rather have dropbox running properly again then to keep my symlinks (at least till DB fixes it).
- my symlinks are super simple, i have folders in dropbox, i need them in another directory, so i symlink them....
Anyways, i deleted all symlinks that had to do anything with dropbox. (and checked with NTFSlinkview.) and rebooted both pc's. Hoping that the problem would be resolved. Sadly not the case. (i tried clicking fix permissions and hardlinks, but dropbox keeps crashing before it gets it done).
Does anyone have any tips?
FYI: ISSUES SYMLINKS
1) If the symlink in inside dropbox pointing to another location then when a file is accessed this is resolved to the true location, and if tyhe file is then updated the operating system notifies interested applications that a file has been updated at trhe location it reolved to (the true location), if that is outside ofd the dropbox folder then DB does not know the file was updated so takes no action, on a DB restart the change is spotted as the application makes a quick pass over all files looking for changes from the database values. No content is checked just file meta data (date time size etc)
2) If the Symlink does not exist on a syncing machine, say it was just generated or was just renamed, then dropbox sees the symlink folder as a new folder and instructs syncing machine to make a new folder and not a symlink
3) recusive symlinks where it points to a location above it or another location that a symlink there points to a location above the first.
THERE IS NO ISSUE WITH SYMLINKS POINTING INTO THE DROIPBOX FOLDER.
When these are used they are resolved to the location of the dropbox and accessed normally.
* Many years ago there was a dropbox symlink app, it found symlinks in dropbox, resolved where they went to and then it monitored all the files at those locations for changes, when one was detected, it tweaked the symlink in the dropbox folder so dropbox thought the symlink updated, and the DB app then looked over the content of the symlinked folders for changes. This was OK unless the resolved location housed 10,000's of files then each change cuased DB to rescane all of them since it was only woken about the symlink location (I expect it is not possible to issue change notifications to sysmlink downstream locations as they are always resolved first.)
