feerlessleadr

1 more question on the SSD optimizer option - would I be able to use the same SSD that I'm using as a cache for the cloud drive as the SSD cache for the Z:\ pool? If so, is there a minimum size I should be looking for? I would be duplicating (initially anyway) about 24 TB worth of data, so not sure if it would really make a difference having a 128/256/512 GB SSD.

Thanks - I'll set this all up once I can get my hands on a good sized SSD drive to use as my cache for the clouddrive.

Just to follow up on Red's problem/question - I am going to be setting up something very similar. My drives are set up as follows: V:\ - Pool set up of multiple physical disks of varying sizes - 25TB total F:\ - Pool set up of 2 cloud drive Partitions (Google Drive, 60TB each) - 120TB total Z:\ - Pool of both V (physical pool) & F (cloud pool) Based on the response from Jaga above, I'm pretty clear on how to accomplish my goal of having F be a mirror of V (and consequently vice-versa). My question comes though in relation to emby, which currently uses the V:\ pool for managing my movies/TV shows. I will oftentimes delete unwanted/watched/etc. movies/shows from the V:\ pool, and If I'm understanding correctly, if I were to continue doing this, if I were to delete a file from the V:\ pool, overnight when balancing takes place (or whenever that is triggered to happen), the deleted files would be added back to V:\ from F:\, since I would have 2x duplication turned on in the new pool Z:\. Is that correct? Assuming that is correct, the obvious solution is to change emby to point to the new Z:\ pool, rather than the V:\ pool. Before I do this however, I was wondering if there was a way to have my programs prioritize reading/writing to the Z:\ pool using the physical disks first (the V:\ pool), then duplicating to the cloud disks (the F:\ pool), since writing to the physical disks would obviously be much quicker. I see that Red was also having challenges with slow read/write times using the combined pool (in my case this would be pool Z:\). His solution to just point to the local pool is great, but that would mean that if I wanted to delete something through emby, I wouldn't be able to, and I would need to use the file explorer to delete the files through the hybrid pool. Just wanted to see if this is something that was fixed either in a new beta release of drive pool/cloud drive, or if there are specific settings that would need to be adjusted to be able to have emby point to the hybrid pool so that I can keep everything clean and tidy. Thanks!

Thanks - I have a good internet connection, so I'm not too worried about re-uploading, the biggest pain is the api limit from drive now.

I currently have a single 100TB volume on drive that I would like to shrink to 50TB, then create a second 50TB volume on drive and pool them together to avoid any problems in the future. When I try to resize the disk using cloud drive, it tells me that I need to check the disk for errors before continuing. When I check the disk for errors, it says that errors are found and need to be corrected, however chkdsk will ultimately freeze at one point or another (for days and days at a time). When I try to shrink the disk using disk manager, I get the same message. Is there anything I can do to shrink this volume, or should I just start fresh with 2 new cloud drives?

Awesome, thanks for clarifying.

Thanks for the response. I guess my question really relates to the following: Once I hit the daily upload limit, after 24 hours passes and the limit is reset, will CloudDrive start uploading again, or will the fact that it is continually trying to upload after the limit is reached cause a longer ban on the upload?

Hi - first of all, thanks for the software, it works great. I'm interested in creating a new cloud drive on my Gsuite account to backup my data, and I wasn't sure how CloudDrive will handle the new upload limits being enforced by Google (soft 750Gb cap per day). I have a 1Gbps line, so I hit the limit between 2-3 hours using rclone, at which point I stop rclone for 24 hours and begin the upload process again. I'm curious however how these new upload limits are handled with CloudDrive? Will CloudDrive stop trying to upload data once the limit is reached and wait the 24 hour period? Or will it keep trying over and over until it can start uploading again? I'm not sure how Google handles these api limits (meaning is it 24 hour ban from when the soft cap is hit, or 24 hours from the last time you try to upload)? Obviously the latter scenario would mean that once the soft cap is reached, unless CloudDrive stops the upload, you would effectively be banned unless CloudDrive is shut down, so that option doesn't seem likely. Before I create the new drive and try to start uploading, I was hoping someone might have some info for me. Thanks!

Are any devs going to respond to this? I am completely unable to use my drive until this problem is fixed. My CRC errors are now over 15k, and I'm still stuck at 10MB to upload.

Just as an update from my end, there is no update. the 'To Upload' is stuck at 10.2MB (.2 MB have been added since my last post), and my CRC errors are over 8k. restarts of the server don't do anything, and I've confirmed there are no filters or anything like that on my network. Similar to eldite, I am unable to detatch the drive, since there is still pending data to be uploaded.

Any advice? I've restarted my computer a number of times, and it hasn't made a difference. My CRC error count is now over 2,200 with still 10MB showing as 'To Upload'.

Just wanted to re-open this thread since the same problem as my initial post has come back again. I am nearing a nearly week-long sync, and the upload is stuck at 10MB for the last few hours, with no upload going on. the status is reporting green, and I'm getting the same Data Error as my original post. here is the drive trace log: https://www.dropbox.com/s/ydror5l5gwk411y/Service.zip?dl=0 I have made sure that there is no web filter on my box or on my router. I've also noticed that the size of my cloud drive as reported in the app is different than that reported in 'My Computer'. It looks like the app says that the current used space of my cloud drive is 10TB, but Windows is reporting the used space as 8.47TB. Any help would be greatly appreciated.

So the only thing I could think of is that I have a smart DNS running on my router, and I have the google DNS servers specifically routed to nowhere (for ads, chromecast, etc.). I just removed everything on the router and rebooted my server. Unfortunately, I was doing all of this remotely, and something happened on my network, so I now can't connect to my machine until I get back home and troubleshoot. With that in mind though, do you think that could have something to do with the problems? ::EDIT:: not sure what happened, but my machine came back online, and with both my smart DNS disabled, as well as the google DNS address routing removed, it has began uploading again, so that must have been the culprit. After everything is uploaded, I'll try to re-enable the smart DNS to see if that causes the same problem, if not, then I'll know for sure it was the google DNS routing. Thanks!

So just as an update, I've let the drive sit since yesterday, and no change. My scheduled sync ran last night, and while cloud drive is reporting the status as green, it is not uploading anything (there is currently about 2TB of information in the 'To Upload' bucket. The same I/O error is ocurring over and over though (see below screenshot)

Hi - I was using Microsoft Synctoy to sync a large number of folders from my local drivepool to the mounted google drive through clouddrive. I was just about to finish the initial sync, and I noticed that the cloud drive was reporting the 'To Upload' as about 60MB, and although it said that it was uploading, the 'To Upload' amount was not dropping as it should. I left if for a few hours yesterday and came back, and it has been stuck at 10MB within 'To Upload' ever since. I am getting an I/O error that has to deal with cyclic redundancy check (see below screenshot): I was doing some searching on the forum, and noticed I wasn't on the latest beta, as the version I was using was 1.0.0.631. I updated to version .696, and my problem has persisted, and it is now also stuck on Pinning Data (as per the screenshot as well). Here is some additional info on my setup: What OS are you using? (run "winver" to check) - I'm running Windows 10 Pro version 1151 (64bit) What version of StableBit CloudDrive are you using? (check the bottom of the UI) - .696 What provider are you using? - Google Drive (unlimited storage, even though Cloud Drive shows 10TB limit) Does the UI have any errors? - See above screenshot. Additionally, please see attached for the zip file of the attached error (both before and after the upgrade). I had to use dropbox since the sizes were too big for the post. https://www.dropbox.com/s/t6qkcsgcqh7yz2w/Service%20-%20696%20Beta.zip?dl=0 https://www.dropbox.com/s/356m9h6aqohzs0j/Service%20-%20Older%20Beta.zip?dl=0