Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  1. Update Status: After continuing to test, I realized that if I tried to create a bucket in anything other than Virginia (US Standard) (ie. N. Calif, or Oregon) I received the error messages. Creating a bucket in Virginia (US Standard) worked just fine. Any reason why a bucket can't be created using CloudDrive for the other regions?
  2. Hi, System: WIN10 i4770 32GB Asus 51AC CloudDrive: BETA I know this is the latest BETA, and there will be issues. That being said, I also happen to find that this version seems very stable and I have been getting great upload speeds to Google and ACD. Now the issue... I connected to S3 using the usual credentials (access/secret) keys. All works as planned. Next, I create a new Stablebit bucket in S3 using the N. Calif. region. Again all works as planned, and I confirmed the bucket was created on S3's site. I go to see what drive letter is assigned and there is no S3 created. I check the error message and it says: Error/ Create / Attach 50.0GB cloud drive. Your previous request to create the named bucket succeeded and you already own it. So, I try to attach it, since it was not created. I then received the following error: This drive has been partially deleted and cannot be attached. So, I try to destroy it, and status bar is green with no error. However, the drive still shows up as "destroyed" and states that it is a destroyed drive. I still have the option to attach it if I want...see where I am going with this (-; Actions to Resolve the error: 1. Shutdown the Stablebit service, and started it again. 2. Clicked the "X" to destroy the drive, and received this error: Delete a CloudDrive Object reference not set to an instance of an object 3. Removed the old bucket in S3, removed my approved credentials, restarted the Stablebit service, and again same issue. Again, I could not find an issue like this one. Apologies if this has been resolved and I did not find it. Any ideas? Thanks
  3. I recently installed .422 on WIN10 and created CloudDrive for both Google Drive and ACD. Both were set on 10mb/10mb chunk and cache size. No issues here. In fact, the uploads were great! For Google, I saw ~20Mbits/s. I didn't test ACD as much, but from the few files I uploaded prior to inserting it into a pool, seemed just fine. My internet connection speeds average: 300mbps down/20mbps up.
  4. Drashna, Thanks for the reply. You can ignore the updated message I just sent via support. I guess I do have concerns about the cloud storage becoming too large. In the end, if I pay for XXGB total, and CloudDrive overwrites the old sectors, then it should not be a factor. Storage providers like S3 may be a factor since I believe you get charged each month based upon the average storage size in a container. Thanks again for following-up and making a great product.
  5. Hello, System: Windows 10 intel i4770 CloudDrive version: BETA 64bit Background/Issue Created a local CloudDrive pointing to Amazon S3. I chose full encryption. The volume/bucket created successfully on S3 as well as the formatting and drive assignment for my local drive. I could see the METADATA GUID, and a few chunk files were created from the process on the S3 bucket. Next, I upload one file and noticed that additional "chunk" files were created in the bucket. After the Stablebit GUI status indicated that all file transfers were completed, I deleted the file from my local CloudDrive. After awhile, I refreshed the S3 bucket and saw that all the chunks were still there...including the new ones that were created when I transferred the file. Here's my newb questions: 1. Am I correct in stating that when I delete a local file which is on my local Stablebit CloudDrive pointing to Amazon S3, it should remove the applicable "chunks" from Amazon S3? 2. How can I be sure that when I delete a large file from my local CloudDrive, the applicable S3 storage bucket size reduces accordingly? 3. Am I off base to think that the two file systems should stay in sync? During my tests, and after waiting quite some time, the S3 bucket never decreased in size even though I deleted the large file(s). Which means Amazon boosts their bottom line at my expense. Thanks, and I searched for this but could not find any discussion on point.
  • Create New...