eldite

Are you talking about the block index database build? ... "this is a one-time operation..." .... I'm on a very quick connection and have about 20TB on a 64TB drive. I didn't sit and watch it, but I think it was a shade under 2 hours.

Turns out it's because the throttling is now hidden. Enable the Information level logging on the ApiHttp module and you can now see that is the throttling message, but since the throttling message has become 'Information' level and the turtle picture is gone, there is no way to know. I suggest that the throttling message be made into a warning again, or the 'Server is temporarily unavailable...' is also moved into information. I'd prefer the prior. Personally, I liked the turtle. Who doesn't like turtles. 21:26:41.0: Information: 0 : [ApiHttp:202] Server is throttling us, waiting 1,792ms and retrying. 21:26:41.0: Warning: 0 : [ApiHttp:115] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 21:26:41.0: Information: 0 : [ApiHttp:115] Server is throttling us, waiting 1,137ms and retrying. 21:26:41.0: Warning: 0 : [ApiHttp:6] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 21:26:41.0: Information: 0 : [ApiHttp:6] Server is throttling us, waiting 1,162ms and retrying. 21:26:41.2: Warning: 0 : [ApiHttp:132] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 21:26:41.2: Information: 0 : [ApiHttp:132] Server is throttling us, waiting 1,716ms and retrying. 21:27:42.8: Warning: 0 : [ApiHttp:190] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 21:27:42.8: Information: 0 : [ApiHttp:190] Server is throttling us, waiting 1,477ms and retrying. 21:27:42.8: Warning: 0 : [ApiHttp:132] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 21:27:42.8: Information: 0 : [ApiHttp:132] Server is throttling us, waiting 1,912ms and retrying. 21:28:54.0: Warning: 0 : [ApiHttp:115] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 21:28:54.0: Information: 0 : [ApiHttp:115] Server is throttling us, waiting 1,953ms and retrying.

Unfortunately no, it's not that It can be replicated easily. It happens every day and drops the drive out pretty quickly if there is any sustained I/O. Just reconnected it 5 minutes ago and it's already happening again. Turning the threads down down makes it less likely to occur. 22:26:18.0: Warning: 0 : [ApiHttp:61] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 22:26:18.1: Warning: 0 : [ApiHttp:188] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 22:41:54.3: Warning: 0 : [ApiHttp:198] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 22:41:54.3: Warning: 0 : [ApiHttp:41] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 22:44:07.0: Warning: 0 : [IoManager:89] Error performing Read I/O operation on provider. Retrying. The read operation failed, see inner exception. 22:44:07.1: Warning: 0 : [IoManager:89] Error processing read request. Thread was being aborted. 22:44:07.1: Warning: 0 : [IoManager:89] Error in read thread. Thread was being aborted. I suspect it's a google limitation, but it would be nice to know what that limitation is.

Hi, I've noticed frequent drive unmounts recently. The log looks like this - the drive still works, but very poorly, then eventually it just drops the drive entirely. It seems like some google side rate limiting, but I'm interested if anyone else is seeing this, or has any ideas of a way to work around it? Cheers 18:03:34.6: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:03:34.6: Warning: 0 : [ApiHttp:166] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:03:34.6: Warning: 0 : [ApiHttp:220] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:03:34.6: Warning: 0 : [ApiHttp:209] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:209] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:205] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:166] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:212] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:219] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:206] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:22.7: Warning: 0 : [ApiHttp:203] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:23.5: Warning: 0 : [ApiHttp:216] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:24.3: Warning: 0 : [ApiHttp:42] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:218] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:208] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:216] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:59.0: Warning: 0 : [ApiHttp:203] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:59.4: Warning: 0 : [ApiHttp:49] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:219] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:203] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:166] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:213] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:220] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.6: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:08:02.2: Warning: 0 : [ApiHttp:205] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:08:02.3: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:08:02.3: Warning: 0 : [ApiHttp:208] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable).

Thanks, yep 45TB. We have gigabit capable fibre to most urban houses now in NZ. It's fantastic and it means using my CloudDrive is faster than many of my external hard drives. I did a small test using MultCloud to copy between Google Drive accounts and it seems to work well. I'll try it with my primary cloud disk. It's $7 per month, but I can live with that. I've really started to rely on CloudDrive (and as a result Google Drive) now, I'm storing all our photos, videos, pc backups, a number of virtual machines, database backups. etc. and of course a fair bit of media. So ensuring I have a redundant copy of the data in another account is quite important to me.

Found my answer to #2 here: http://community.covecube.com/index.php?/topic/2891-migrating-data-from-one-gdrive-to-another/?hl=%2Bcopy+%2Bclouddrive Shame you can't mount both drives on the same system. Having the ability to "re-id" a drive would be very nice, but I understand the challenge from a development perspective. I might have to run another copy of CloudDrive in a VM. Any info on the drop-outs would still be appreciated.

Hi, A couple of questions 1. Recently I've noticed by CloudDrive has dropped out a lot more than usual. I was able to partially mitigate this by increasing the retry count in the settings to 30. The message says something like "cloud drive was not able to download data from the provider" or something like that. The log usually has a lot of this in it "[ApiGoogleDrive:44] Google Drive returned error (userRateLimitExceeded): User Rate Limit Exceeded". It used to be very reliable, but recently much, much, much less so. It drops out a lot with heavier usage. Has anyone else been experiencing this? 2. I run two cloud drives on google, under separate accounts which synchronize from to the other for redundancy. When I upgrade cloud drive, I attach one disk, test it for a week, then attach the other and re-enable the sync. Recently my ISP called up and said I'm running close to the line on their "fair use policy" (45TB last month). Q2a) If I do a direct google drive to google drive copy on another account of the raw files, then I attach cloud drive to that replicated drive, will it work? Q2b) Does anyone know of a service or way to do a google drive to google drive copy between accounts? Cheers

With your connection, set you chunk size to 20MB, set your minimum download size to 20MB, 400 to 800MB prefetch and 20 threads, you should get solid download performance (100Mbps+) It will take longer to load initially on startup, but then it will play smoothly throughout the video. Make sure you've got a solid SSD cache disk.

It is likely your cache disk has less than 5GB free? When that happens it throttles the copy speed down to the connection speed.

Today I see this comment in the changelog: 1.0.0.800 * [D] [issue #27311] Fixed a memory leak in the prefetcher. Thank you !!

It's not your settings, it's a problem with the software. All you can do is wait until it's fixed. I think it is a problem with disks created in the latest version, or with large disks. I'm using 1.0.0.784. I have an old virtual disk created with version 1.0.0.4xx and that disk gets 40-50Mbit download. I'm was not happy with that speed because I've got a 100Mbit connection. I had read that you could get MUCH faster speeds with a 20MB provider chunk size. So I decided to upgrade to the latest version and create a new disk with 20MB chunks. It is super slow (10Mbit) download from my new disk. I noticed it was using a lot of CPU (and it's a good cpu) so I tried an unecrypted drive too with 20MB chunks. That's the same speed (10Mbit) and uses a bit less CPU. The virtual disk that was created under the old version still pulls 40-50Mbit on the latest version, but the virtual disks created under the latest version max out at 10Mbit. My conclusion is that disks created with the latest version are not usable. I would give it a few months and try again then.

More of a bug report than a forum question. There is a memory leak when the drive dismounts (which happens all the damn time, by the way). Attached are the imagery of PoolMon showing CLFS (Cloud File System Driver) taking up 7GB of my 8GB of RAM. It's hard to get this screenshot because the PC is basically unusable when you have a non-paged pool memory area taking up your entire RAM. This is on the latest version (784 at time of writing), but I have also experienced the exact same thing on all other versions. This means that when connectivity fails, it then uses up all your ram and freezes the PC. I see other people are reporting the same thing. Hopefully it can be prioritized with this photographic evidence These ongoing issues (retry count exceeded, memory leak, corrupt disks after upgrade) are slowly wearing down my love of this product. Thanks guys

I was on an old version 1.0.0.4xx? I think. I upgraded yesterday (24th) and a similar thing. All data on the drive become totally corrupt, e.g. none of the files would open succesfully. After clearing cache and then detaching and re-attaching. The drive no longer mounts in windows. Tried re-authing too. Cloud drive connects, but windows it shows an a brand new disk and windows disk management asks me if I want to initialize this disk. Interestingly, I had 2 drives, under separate accounts, one is encrypted, one is not. This was the encrypted one, the other one seems okay. It appears to be toast. Luckily I have it all backed up, but it will be 25 day upload for me to restore it... not really looking forward to that.

Yes, not having to click the "Retry" for remounting would be a BIG feature, it could auto retry every after 5, 10, 20, 30, 1hrs, 2 hrs, etc.

As mentioned, after I upgraded to the latest version the "CRC Errors" turned into "I/O Errors". Then I checked my event log, I found windows was reporting timeouts trying to read from the disk. I removed the disk and restarted CloudDrive. I used a new cache drive and all good. So I assume it was my cache disk (however I have recently done a full read/write of the entire drive with no issues). Running fine since changing the cache disk. I ran a chkdsk on the Cloud drive because obviously some data will be missing/invalid that was on the cache disk and could not be uploaded.