When one of the menu options are selected, StableBit CloudDrive will stop writing data to the storage provider as soon as an error is encountered. Normally, failed writes are retried, and additional data continues to upload.

This is useful if you are attempting to use an external tool to record a specific but rare error from the storage provider.

The type of error that will cause the writing to pause can be narrowed down further by the available menu options:

• Any Error

  When enabled, writing will be paused on the first storage provider error encountered. Any storage provider error will trigger this.

• Security Error

  When enabled, writing will be paused on the first storage provider security error encountered.

  Each storage provider defines what it considers a security error. For example, most HTTP-based storage providers will consider a HTTP status code 403 to be a security error.

• HTTP Error

  When enabled, writing will be paused on encountering the first HTTP error with one or more specific status codes. You can specify more than one status code separated by commas.

  This option only applies to HTTP-based storage providers.

• Write Verification Error

  When enabled, writing will be paused on encountering the first write verification error (also known as an upload verification error). See Upload Verification for information on how to enable and disable it for your cloud drive.

Optimizations enable or disable certain code optimizations in StableBit CloudDrive. Normally, all optimizations should be enabled.

• Handle Caching

  When enabled, open handles to the local cache will be reused among different I/O requests. This is done in order to avoid opening and closing the cache files for each I/O request.

• RAM Cache

  When enabled, RAM will be used to assist I/O requests in order to avoid issuing redundant requests to the storage provider. The size of the RAM cache can be set when Creating a Drive under Advanced Settings > Chunk Cache Size.

• Short Circuiting

  When enabled, this optimization works under 2 specific scenarios:

  1. When a chunk is being written, and a read request comes in for a part of that chunk, the write will immediately pause, copy the required data into the read request and resume writing. This makes sure that the read request can complete immediately.

  2. When a chunk is being read, and other read requests come in for a range of data that is already being read. Instead of issuing separate requests to the storage provider for the same data, the existing data will be used to satisfy all of the requests.

• Write Thread Boosting

  When enabled, if multiple writes need to perform a read-modify-write on the same chunk of data, an attempt will be made to combine all of them into 3 steps that require 2 storage provider I/O requests.

  1. The whole chunk will be read from the storage provider.

  2. Each write will apply their individual change to the chunk that was read in.

  3. The entire chunk will be written back to the storage provider..

  In certain cases, such as when the storage provider returns an error, this optimization won't be applied, and the write requests may be split up for individual processing.

• Kernel Read Buffering

  When enabled, a shared non-paged kernel memory space will be used to send data directly to the virtual disk when servicing read requests.

  Otherwise, the data will have to be written out to the local cache and then read back in by the virtual disk.

• Write Pre-buffering

  When enabled, for all of the data that needs to be written to the storage provider, a single dedicated thread will be used to pre-buffer that data from the local cache.

  Otherwise, multiple upload threads may have to read from the local cache at the same time. This can cause disk thrashing, thereby slowing down the performance of the local cache disk.

Options to simulate various storage provider errors are available here.

All of these error simulations will be turned off on the next reboot (or when the StableBit CloudDrive service restarts).

• Simulate Read Errors

  When enabled, there will be a 10% chance that a storage provider read will return a simulated error.

• Simulate Write Errors

  When enabled, there will be a 10% chance that a storage provider write will return a simulated error.

• Simulate Read Failures

  When enabled, there will be a 100% chance that a storage provider read will return a simulated error.

• Simulate Write Failures

  When enabled, there will be a 100% chance that a storage provider write will return a simulated error.

• Simulate Security Errors

  When enabled, there will be a 100% chance that a security error will be simulated on either a storage provider read or write .

• Include Mounting in Error Simulation

  Normally error simulation doesn't prevent the drive from mounting, because the mount process is not included in the error simulation.

  When enabled together with simulating read failures or simulating security errors, the drive will return an appropriate simulated error when mounting.

This opens the Service Log window.

I/O Requests and Provider I/O will only be shown for the cloud drive that is selected here.

Opens up Drive Details for the selected cloud drive.

When disabled, uploading to the storage provider will be paused for the current cloud drive.

This is the same as unchecking Upload Threads under I/O Performance > Threads.

When disabled, prefetch requests will not be shown in I/O Requests or in Provider I/O.

When disabled, read requests will not be shown in I/O Requests or in Provider I/O.

When disabled, write requests will not be shown in I/O Requests or in Provider I/O.

When disabled, completed requests will not be shown in Provider I/O after they end.

When enabled, I/O Requests and Provider I/O will pause updating. This will let you examine the information contained there in detail.

This is a prefetch read request.

This is a non-prefetch read request.

This is a write request.

This is a non-prefetch read request.

This is a prefetch read request.

This is a write request.

This request ended successfully. The item will be shown for 4 seconds after it ends.

This request ended unsuccessfully. Selecting it will show the error message in the Status Bar. The item will be shown for 15 seconds after it ends.