Code Change Request

# 27641

Back to Code Changes

Christopher
Technical Support
StableBit CloudDrive
1.0.2.929
Windows Server 2012 R2
Public
Alex
* [D] [Issue #27641] I/O queues were sometimes not being purged when a cloud drive was unmounted.

Additionally, there was a race condition where if a drive was forcefully unmounted, ongoing I/O requests were not always being purged from the I/O queues, and that would cause the system to crash.
Public
Alex
I'm seeing a bunch of these in the log:

CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-22 06:08:40Z 18099518581
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-22 06:08:46Z 18113965692
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-22 06:09:16Z 18185447351
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-22 06:09:22Z 18201449319
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-22 06:09:24Z 18205826704
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-22 09:26:27Z 46998963358
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-22 09:26:34Z 47016911336

...

CloudDrive.Service.exe Warning 0 [ApiGoogleDrive:149] Google Drive returned error (notFound): File not found: 0B6bsfglELGm3Y1pIN0NhbWJ4QlE. 2017-09-25 07:10:10Z 658327816493
CloudDrive.Service.exe Warning 0 [ApiHttp:149] HTTP protocol exception (Code=NotFound). 2017-09-25 07:10:10Z 658327820323
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-25 07:59:46Z 665573878884
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-25 08:00:12Z 665636710231
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-25 08:00:13Z 665640191069
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-25 08:02:32Z 665978997036
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-25 08:02:35Z 665985644097
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-25 08:02:35Z 665985756627
CloudDrive.Service.exe Warning 0 [CloudDrive] Read complete failed: Element not found 2017-09-25 08:02:37Z 665990776470

This means that a chunk of data that we know has to exist on Google Drive was not found, so we have no choice but to fail the read request (final critical failure). This is of course very bad.
Public
Alex
May be related to this:

.947
...
* [D] [Issue #27657] 0 length ranges were allowed.
    - If read / write / pin maps contain invalid ranges, the maps will automatically recover using unsafe start recovery on the next 
      mount.

If that's the case, newer builds will recover from this automatically.