Right-click won't work on odrive icon in icon tray (Windows 10 Anniversary)

Troubleshooting
41

Hi @shane,
Sorry. Yes it would need to be restarted to do this, since diagnostics can not be triggered from the CLI.

If you restart odrive, see if you can have it run for a little bit before sending.

Thanks!

42

Hi Tony,

Sent. Hope this help diagnose some issues. I have switched to limited upload and now about 4K waiting.

Regards
Shane

43

Hi Tony,

It is still becoming full non-responsive after a few hours. After about 6 hours it looks like it stopped being responsive and nothing gets synced and CLI status update doesn’t return anything until i kill the process. Is there a way to disable the tray menu system through CLI?

Regards
Shane

44

Sorry for not having read any of the responses, but setting odrive to empty trash immediately and letting it sit for several hours helped me a lot.

45

Hi @shane,
It looks like it is running into a memory constraint due to the number of objects piling up. I actually wasn’t able to get a clean diagnostic (it was an exception dump instead). Is it possible to break up the files into smaller chunks to make them easier to digest?

Can you tell me how many files/folders we are talking about?

46

I’d just like to add to this topic another issue that I think might be relative to this problem. It has to do with OSX and NTFS volumes.

I have an external NTFS drive connected to OSX Sierra of which my odrive folder exists at root level. OSX’s built in NTFS drivers are terrible and eventually cause corruption of the drive (so far temporarily), something having to do with journal flags, dirty unmounts or similar? The 3rd party Paragon NTFS driver software resolves this but at this time has proven to be incompatible with odrive causing mass CPU usage so I have elected to continue using the native NTFS drivers.

Anyway, when this occurs, file and folder access is wonky, for example, my root odrive folder now has thousands of files that shouldn’t exist there but should actually reside within sub-folders. Checking dmesg from the command prompt tells me what to do and that the drive is dirty. I then boot into Windows, the OS I loathe and repair the drive by letting it fix the indexes/journal.

This always seems to fix the problem and my files so far have always all recovered to the right locations but I still end up with thousands of files in the deleted items list resulting in this problem (reported in this thread) which seems apparent that it is due to the sheer volume of files in the deleted items list. The very same files that were showing up in the root folder but again appear to be copies from the OSX NTFS driver mishap.

I need my external drive to be readable and writeable across OSX, Windows and Linux as in my line of work I use all 3. I also need to support large folder depth and large files over 4GB as many are images of systems. I’ve tried exFat but end up with issues in Linux taking me back to NTFS as the lesser compromise. I feel like I can’t win here, any suggestions?

47

Hi @p_ingram3541,
This won’t be a problem in the next generation of odrive, it is something that can be hit, currently.

When you hit this case what do you end up doing? Are you using the CLI command to empty the trash?

48

At this point I am worried about file loss. I have shut down the sync client and am running to go pick up another drive so I can sync everything down from the cloud on a fresh OS and then run an extensive compare against the two drives to find out what is junk and can be delete and or if I have any lost data I should be concerned about. I love odrive but I am worried for my data, if you don’t mind me asking, what is the best approach to protecting my data in the cloud from syncing up when drives become corrupt?

49

Hi @p_ingram3541,
I didn’t know that the NTFS support on MacOS was that bad. Sounds awful.

Since you need to access data across different OS’s, can you instead use odrive’s progressive sync and unsync to maintain separate storage on each machine, but only locally caching the items you need at that time? Or, do you need to have all of that data available on all systems?

As for preventing syncing corrupted data, there isn’t a whole lot that can be done unless you are keeping your files as placeholders. There is no data to corrupt on a placeholder file. There is a post here regarding ransomeware, which I think has some relevant info that applies here, if you want to give it a look.

50

Thx @Tony I got everything situated now. I have chosen to keep an offline copy that I will sync from a Windows environment at periodic intervals so that I can continue to use my portable NTFS drive across all 3 OS’s. I only need to sync down at will so the placeholder approach is a great suggestion and eliminates having to have different drives for different OS’s.

1 Like