Jump to content

Martixingwei

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Martixingwei

  1. 5 hours ago, Christopher (Drashna) said:

    FAQ answers that, as did I, above.  You can generate your own app API keys and use those, these are configured in "C:\ProgramData\StableBit CloudDrive\ProviderSettings.json" file. 

    The Google Drive Provider will be marked as "expirmental"/"deprecated".  This means that new installations, the provider will be hidden by default.  You can enable it by enabling experimental providers.   However, if you already have connected to Google Drive on a system, then it will stay visible. 

    Fully outlined here: 
    https://wiki.covecube.com/StableBit_CloudDrive_Q7941147

    Is it possible to change the already mounted drive's API key? I have a mounted Google Drive with ~1TB remaining to upload, but the default API key seems to be severely throttled, uploading in a very unstable manner, stuck at 0bit/s at more than 50% of the time.

  2. 2 hours ago, Christopher (Drashna) said:

    I'll have to ask to double check, but most likely, this would be us deactivating our app API key.  You'd need to set up your own API key to continue using the software, or download all of the data from Google Drive, and use the converter tool to convert it to the local disk provider format.

    Using my own API key would be a totally viable solution for me. Hopefully, I can still use cloud drive with google drive for future! Also, maybe integrating with rclone will also be a solution allowing more flexible backend choices for advanced users.

  3. What will happen after May 15th? The majority of my data is on my Google workspace enterprise account. I do not think it is possible for me to find another storage provider to host my data economically. Will all data have stored through cloud drive being inaccessible for me after that date? Is it possible to use my own API keys to continue using Google Drive as a provider for cloud drive?

  4. On 5/23/2023 at 4:46 PM, Shane said:

    Just to check, igobythisname, did you use the Resize... option to shrink the drive after deleting the data from it? Running the Cleanup... option won't shrink the drive on its own, the shrinking has to be done first (also the Resize should attempt to automatically Cleanup after it finishes the shrink).

    Resize does not work as the minimum size is limited to the cloud usage not actual disk usage. I got a 127TB drive with 10TB data in it and 100TB of cloud usage. It only allows me to resize to 100TB not 10TB.

  5. See the wiki about advanced settings: http://wiki.covecube.com/StableBit_CloudDrive_Advanced_Settings

     

    Specifically, this:

     

    • CloudFsDisk_MaximumConsecutiveIoFailures - This setting controls how many unrecoverable I/O failures can occur before the drive is forcifully unmounted from the system. Increasing or disabling this setting can cause issues where the system may hang/lock up, as Windows will wait on the I/O to finish. The window for these errors is 120 seconds, and if this time is exceeded without an error, the count is reset. The default value for this is "3".

     

    Adjust this to 8 to 10 or so. See if that fixes it. CloudDrive will detach your drive to prevent system lockups, but Google has hiccups that are temporary and solved by raising this number a bit. Don't go too high, though, as some sort of genuine failure will lock up your system--and you want CloudDrive to work around those. 

    My internet sometime drops for a few minutes to one hour, the number of consecutive failures could be huge. It is not safe to set that threshold too high, so I hope my CloudDrive could first unmounts the drive, keeps testing for connection, and then auto reconnect and remount everything.

×
×
  • Create New...