Jump to content

raidz

Members
  • Posts

    12
  • Joined

  • Last visited

  • Days Won

    1

raidz last won the day on April 9 2016

raidz had the most liked content!

raidz's Achievements

Member

Member (2/3)

4

Reputation

  1. So I thought when I detached a drive last week I accidentally hit destroy instead of detach and wrote it off as my own stupidity. I just detached another drive today and CD destroyed it. I lost 40 TBs of data. DO NOT detach your cloud drive until they figure this out. I am extremely pissed to say the least. I have lost two drives now in the past 7 days, some with data I did not have backed up in another place. This is extremely unacceptable and I warn all of you of putting anything worth your time on these drives until they make this software more reliable. I guess the software is listed as beta, so my own fault for thinking it wouldn't ruin a drive in one fell swoop. Data actually isn't gone but the files they wrote to have no previous versions so it looks like I cannot recover.
  2. This issue is pretty much making cd unusable after a few hours for me at this point. Restarting every few hours is a bad solution. Any progress being made towards a fix on this Christopher?
  3. It looks like we are actually discussing this same issue here: http://community.covecube.com/index.php?/topic/2334-poor-performance-google-drive-not-rate-limit/
  4. My Chunk size is at 100mb, Minimum download at 10mb, Download threads at 12 and Upload Threads at 6. No matter how many threads I set (more or less) it is still slow as molasses (on a 1gbit/1gbit line). Download speeds have decreased as well due to delay in thread response time. This started happening to me after .726 and has not been different since. I do believe this might has to do with Google limiting API request but also think it is something they changed in the software that is triggering it unless Google just made a big change to how they handle requests.
  5. I am seeing the exact same issues as these two guys. I uploaded logs about a week ago so hopefully Alex can give this some time soon.
  6. Seconded. I know exactly what @steffenmand is talking about and it can get quite annoying but not unbearable.
  7. Unless .594 reverted the changes in .593 The downloading same parts over and over issue still exists. It doesn't seem to be as bad but still very annoying and a big waste of bandwidth. It doesn't download them 20 times in a row but maybe 10 now, it doesn't seem to happen all the time either.
  8. Agreed, I am seeing this issue (with multiple files) as well. I would say this newest build is a step in the right direction but the prefetcher still needs better logic, and I still see multiple chunks being downloaded over and over at certain points, but not nearly as often though.
  9. I am testing now and it looks to be fixed! Very exciting!
  10. Thanks, as you know from the ticket I posted, without this fixed my CloudDrive is pretty much unusable for my intentions. I think @steffenmand's guess is most likely the correct one in that CloudDrive thinks it is still getting 1-2mb chunks as anything above auto for minimal download has the same chunk downloading over and over. Hope Alex gets going on this soon as this seems like one of the most replied to threads in this forum. Appreciate your efforts so far, this is a pretty slick piece of software.
  11. Is this still being looked into? Happening to me all the time, lots of wasted bandwidth with no real benefit.
  12. I am getting the exact same issues, very annoying.
×
×
  • Create New...