It would be nice if clouddrive can empty cache when it get at some %.
I'm not entirely sure what you mean by this, but it does basically. But it actively avoids doing so if it can.
Sry, i forget to answer.
Different drives. My unraid machine and clouddrive machine is separated. I mount my clouddrive share over gigabit network. And when i copy to unraid machine to clouddrive share then everything freezes. Clouddrive can't upload or download data after file copy is done.
It is somewhat better when i use ssd as cache drive. With HDD im starting to get bandwith errors and so on. Maybe HDD can't handle incoming LAN transfer and same time uploading/downloading data.
24/7 i get 300/300, i tried even 500/500 connection but same thing..
To clarify, how is everything setup?
What provider are you using for StableBit CloudDrive?
Is this the local disk provider? WIndows Share Provider?
What system are you using for the copies?
Where are you copying to and from?
With the last release I am seeing similar - where my machine seems to freeze...A LOT. When I FIRST purchased the software, I had set it up and was seeing some throttling issues. I attributed that to the size of my Cache drive and the throttling that needed to happen to keep things happy.
Then, sometime last week (I do not recall the day), I was offered a new version. Realizing this is still beta and that we were coming close to the cycle - I figured why not?
In my setup:
I have 13 clouddrives setup.
1 box.com, 2 dropbox, 10 Google Drive (not the paid cloud drives, but the provided ones for personal use).
I pooled them using DrivePool and disabled any replication / balancing / etc. Just act as a single large drive putting files where ever there was space.
With this version, I now have to re-authenticate to each drive nearly every 12 hours!
My fileserver (Windows Home Server 2012) was getting so bogged down and seemingly SLOW that I actually just let all the drives finish asking for re-authentication. At this point, more than 1/2 of my drives are sitting waiting to be authenticated again - BUT my machine is now stable or responsive again. I am assuming something in the kernel level was waiting on something and instead of giving up the processor while it waited, it just sat there hogging things.
BTW, DrivePOOL is unhappy with me at this time as most drives are not there. Good thing this is not critical data!
This may be a completely unrelated issues to ufi56's issue, actually.
Specifically, in the new versions, we are forcibly indexing the entire contents of the folder's used for CloudDrive, on certain providers (Box, DropBox, Google Drive, Amazon CLoud Drive).
This has to complete before each drive is usable. However, this is a one time process, and shouldn't happen again.
That said, if there isn't enough bandwidth, it may cause issues. And if there are too many issues in a short period of time, the software will unmount the drive.
This is done explicitly to prevent the sort of freezing you've mentioned. In fact, Windows can (will) lag/lock up when waiting on IO. Unmounting the drive will fix the issue.
That said, at least for the indexing process, it may be too sensitive to errors for your connection. This can be tweaked here:
Set "CloudFsDisk_MaximumConsecutiveIoFailures" to "10" and reboot the system. This may prevent the drives from unmounting and requiring reauthorization.