Code Change Request

Public

* [Issue #27053] Default to 4096 bytes per sector for new drives.

* [Issue #27053] Do not allow the local cache to be stored on a disk that has > bytes per sector than the cloud drive being created.

Public

* [D] [Issue #27053] When 3 consecutive unrecoverable I/O errors occur in the kernel driver, the drive will be force unmounted from the system. For example, if a read 

                     request can't be serviced because the data in the cloud is not accessible, we have to fail that read request, and that's considered an unrecoverable 

                     I/O error. Disk read timeouts due to a non-responsive system service are also considered unrecoverable I/O errors. The force unmount is managed 

                     entirely by the kernel driver and does not involve any user mode component. The force unmount occurs in order to prevent the system from locking up 

                     in cases where the drive's data becomes inaccessible (for various reasons) after the drive is successfully mounted.

Public

* [Issue #27053] Error reports will now be written out when drive mounts fail due to a problem with the provider.

* [Issue #27053] When a drive mounts, it will now perform a check to make sure that it can properly communicate with its data provider. If it can't, 

                 due to a security error or some other type of error, it will go into a pseudo-mounted state. In this state, the data structures necessary 

                 to work with the drive will be loaded, but no virtual disk will be spawned in Windows.

                    - The user will be informed via the StableBit CloudDrive UI that there was a problem mounting the drive, and will be offered different options to 

                      resolve the issue, depending on the nature of the error.

                    - If there is a security error, the user will be offered the option to reauthorize. If the reauthorization succeeds the drive will be mounted.

                    - If there is a communications error with the provider, the user will be offered the chance to correct the problem and to retry the mount.

                    - At all times, there will be an option available to destroy the drive from the local system entirely. If there is a communication error with the 

                      provider, the drive's data that's stored at the provider will not be deleted. The data can be deleted at a later time, once communication is 

                      restored.

Public