Jump to content

mtnezdilarduya

Members
  • Posts

    1
  • Joined

  • Last visited

Posts posted by mtnezdilarduya

  1. On 1/9/2021 at 8:55 PM, Christopher (Drashna) said:

    This can happen any time that the system has an unsafe shutdown. A forced reset, for instance. Or if the CloudDrive service doesn't get closed out properly (eg, if you "end process" on it).

    And how long this takes depends on the size of the drive, the size of the chunks, your connection speed, the number of threads for download, and the like. 

     

    As for permission issues, you may need to run CHKDSK on the drive.  And if that doesn't fix it, we do have a guide on how to reset permissions: 
    https://wiki.covecube.com/StableBit_DrivePool_Q5510455

    Update:

    The first drive just finished mounting. And right now, the situation is that the amount of data that was previously stored as 'Cached' is now in 'To Upload'...Is this the expected behavior? Shouldn't be enough to invalidate the read cache? why is it being uploaded again?

     

     

     

    Hi Christopher,

     

    After an unexpected reboot on my computer, Cloud Drive is taking so long to recover my 3 drives (GDrive).

    After reading a couple threads apart from this one, I reckon that cache size is what mostly affects here. But, should the cached data (read cache) matter here? Or only the 'To Upload' part (write cache)? Or both?. In my case, two out the three drives had practically nothing in 'To upload', and they're also taking lots of time.

     

    In order to reduce recovery time in case of computer 'unsafe' reboot, should I reduce both cache-types? Thank you very much

×
×
  • Create New...