Jump to content

amilligan

Members
  • Posts

    2
  • Joined

  • Last visited

amilligan's Achievements

Newbie

Newbie (1/3)

0

Reputation

  1. The weird part was drivepool did not recognize that most of the data had already been cleared out of the cache drive (and uploaded to the cloud). I finally restarted my server. It took at least an hour to reboot. Then Clouddrive was mad - said I did an unsafe shutdown and was having to re-synchronize. I also had to ask drivepool to re-check duplication a second time to make it happy, but now it's acting as it should with no out of space errors. The one thing I find odd is the time drivepool takes to make an additional copy for the cloud. There a basically open SSD drive waiting to cache the data and it takes hours to make a copy and provide it for cloud. It sounds like it should be fast based on the link above discussing how the cache works. Any thoughts on why it is slow? In case it matters here is what I am doing: 1. 3 local hard drives (4TB, 4TB, 1.5TB) 2. 1 cloud drive (800GB) 3. Using folder duplication. 4. Most folders have 2 copies on local drives and some only 1. 5. Pictures folder had 3 copies - all on local drives and completed before I added the cloud drive. 6. Once I added the cloud drive I went into drivepool / pool options / balancing / file placement and deselected the cloud drive for all folders except the Pictures folder. 7. Then started changing folders under Pictures to have 4 copies - the cloud drive was the only option to make the 4th copy. 8. I did not do the entire folder (~275GB) at once - a few folders at a time. Can you tell I'm worried about losing any photos? ;-)
  2. I don't see that a "max size used by the cache" option was added. I'm running 1.0.0.442 and have I/O Throttled errors because (supposedly) my drive D: is out of space. The error says: "I/O Throttled Cloud drive (I:\) - Dropbox is having trouble writing data to the local disk (D:\). This error has occurred 53,567 time. Your local disk (D:\) has run out of disk space. Continuing to get this error can affect the data integrity of your cloud drive." Drive D: is the second partition of the SSD boot drive and is 178GB in size. My cloud drive is 800 GB on Dropbox with a 5.00 GB cache. I recently added another duplicate to a folder so that a copy would be created on the cloud drive. Currently duplication is at 87.5%, but going very slow - apparently throttled by my upload speed to Dropbox. Clouddrive says there is still 14.7 GB to upload and if I look at the properties of the CloudPart folder on D: is corresponds with size on disk 14.7 GB (and size 800 GB). I've got a couple other folders on the D: drive and all totaled size on disk is currently 54.6 GB (and size 839 GB). So why does Windows Explorer say 3.87 GB free of 178 GB? Why is Drivepool basically stopped at 87.5% because it (apparently) also thinks drive D: is full? This situation is also affecting the response of the server and general transfer speed of the shared folders.
×
×
  • Create New...