Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  1. That makes a whole bunch of sense now! Ok, now I have a better understanding. Yes duplication is on for sure and I wasn't quite sure if that was the case. You've solved the puzzle for me Chris, thank you so much!
  2. I technically have two "cloud" drives. One using Google Drive, and one using File Share to a TeraStation but of course is using a cache drive created by Stablebit Cloud Drive. Both cloud drives use their own hard drive to store cache data. What was happening is when Google Drive had its cache drive filled up, it stated it was throttling that drive. Terastation was showing plenty of Cache space, Cloud Drive app did not state it was throttling it. However, I noticed the write speeds did resemble throttled speeds when I saw writing actions to the terastation in Stablebit Drive Pool performance section. I'm curious if maybe this is by design? Writes to cache drives that have a disk full throttle all of them? Side note: my cache drive has emptied a little and balancing has gotten more organized. Not much of a problem now. Above all, thank you so much for reaching out Chris. Again, feel free to ask any question or if you wish me to provide more details. I'll even allow remote access to review.
  3. Hello! I have a little strange problem. When one of my cloud cache drives fills to the rim with cached data and naturally throttles writes to "it". I instead get throttle writes to ALL disks within the pool. The cloud drive is apart of the Stablebit Pool. What I had thought to circumvent this issue when I have a lot of data come in I have new writes write to other disks and then later balance to the cloud drive. I only have a 50MB upload speed. I'm scratching my head and wondering why this is happening? When write throttle is activated in CloudDrive, the speed gets reduced to 500-520 KB/s. Also, would this only throttle the CloudDrives specifically? Please let me know if you require more detail. Thank you guys so much!
  4. Hello! So I am VERY happy with all of the Stablebit products. But there's one thing that seems to be shooting myself in the foot. (I think) EDIT: So I began with my drives already filled to 60% before adding a cloud drive. This is to explain why my disks are so full already. The balancer wants to throw everything into my cloud drive according to the blue arrows. I'm not sure why it would as that would be my entire data? Why does it think this is redundant? I have rules set to default and drives are healthy. While the balancer does do this it chokes the disk that the cloud cache is sitting on until it has to throttle due to maxing out the cache drive. I have a truck load of data that comes into the pool from a virtual machine but I have to sometimes set file placement rules (via plugin) to NOT place data on the cloud pool aka cloud cache drive. I typically have it go to Disk 1 as the balancer likes to empty that one. I'm terrible at explaining things. Forgive me. If you need more details I will respond ASAP. Or, if you would like to advise on best practices what I should do. Thank you amazing team!
  • Create New...