steffenmand

Yea i know those settings and none of those changes the global limit So i think the global thread settings are either hidden or hardcoded into the code - although i dont get the reason as the limit should be per account and not across all your drives

Are you sure this is also an option when using CloudDrive alone? Wanted to try and edit my settings, but for some reason its empty now :D - Did they change something in recent versions casusing the Settings.json to be empty (0 bytes)?

If you have a lot of content then expect it to take days... Alternatively use recuva to recover files

Hi, Im currently using a 32 core system (64 threads) but i simply cant see Stablebit using more than 20 threads maximum at any given time, eventhough i have 10 drives split over 5 different users. Are the limits for a drive (20 threads) also the global max ? - If so is it possible to get it changed to 20 threads PER USER as each user has its own API limits? If its not limited globally, what could the issue be when threads start to be few if multiple drives are in use at the same time ? - i use NVMe drives and they are not reaching their peaks at all. In

I actually like this feature request - being able to cache headers of your files up to X GB. It would for certain improve a lot of stuff in various usecases

The newest beta works great for me - i still have a great speeds and the drives are upgrading fine (25% per day)! Only annoying bug i have atm is that if i try to attach a new drive, then it will fail and give me a folder i cant delete. After a reboot the drive will mount (although it said it failed, but due to the folder being there) but not upgrade as it is supposed to. So since im moving my drives to a new server im only able to move and upgrade 1 drive at a time (although my drives are split over 5 google accounts and in theory have api limits on each account).

1306 doesnt show any files being moved though like 1305... so dont know if it works or not :-P

I can see chunks being moved on my drive, so i know its running! We just have to give it time :-)

Mine is still going... complaining about Userlimitexceeded. Going on Google i can see it has not moved files since the night to sunday... so for me atleast it will take a looooooong time if we dont get a higher API rate limit! And this is the first drive i have out of 12

The reindexing you saw was normal since waaaay back. Its to avoid corruption, then it rebuilds the chunk database by going through them 1 by 1 The numbers you saw were chunk id's

Seems to make no difference here... Same error and still no % counter. My guess is that you guys got to a certain point before the limit was reached, where mine didnt get started. Anyway i hope they will have a fix for this soon - just sucks that stuff like this always have to happen in weekends

What field does the key go in? And is it in ProviderSettings.json?

Your drive is reindexing - it can take a while. Most likely due to og being closed wrong

Thats the one i got :-)