Search the Community

In Windows when deleting something like 100,000 files, it's quick and completes in a few seconds. This is a high-level delete operation. IO operations with Drivepool all take a much longer time than Windows. Things such as: In explorer: Right-click folder > properties (to view number of files, folders, size) OK, I'm not sure this one is drastically slower (if at all). Discovery takes a long time for a delete. Like #1 above. A delete operation take a long time for a large number of files. I'm talking like 50-150 IOPS, which makes me think this is related to disk IOPS. Can these operations be dependent on any settings for my pool, or is this just part of the territory for what Drivepool does beneath the surface? Correct if I'm wrong: operations in Drivepool seem to be limited by the IOPS of the disk(s) in question.

I uploaded the wrong folder to my drive, so I went ahead and deleted it but CloudDrive was still busy uploading all the remaining files (~18GB) I copied over. Is there any way to cancel this, by deleting the upload cache for example? When detaching the drive it gives the error that I'm busy uploading so that isn't really an option. Thanks in advance

Hello, all! I have been testing out CloudDrive's latest beta, and run into an issue. I had some odd errors, unrelated to CloudDrive, on my server, which resuled in my decision to destroy my 10TB cloud drive [on two separate occasions]. As part of a reinstall, I decided to delete the CloudDrive folder on my Google Drive, as well, as I will reauthorize and recreate another drive later. However, now I have found an issue. My Google Drive still reports as having over a TB in use, which is approximately what I had on the drive prior to deleting it. While I do not see any chunk files, I can perform a search by looking for title:chunk and get results. It looks like I still have all of the chunks from the destroyed drives, even if I do not actively see them in the Drive directory. I would like to find a method to delete them. Is this stubborn chunk data staying behind normal? Can I utilize CloudDrive to delete them? Doing so manually would be a bit impracticable. I see in my research that Google gives access to an API for deleting files. Will I need to create my own script to mass delete these pseudo-hidden chunk files? Lots of questions, I know. Let me know if I can provide any helpful data. I haven't deleted/uninstalled CloudDrive, so any logs it has created by default would still exist. Windows Server 2012 R2 Datacenter x64 16GB RAM, 3.5Ghz CPU CloudDrive at latest version as of May 17, 2016 -Tomas Z.