steffenmand
-
Posts
418 -
Joined
-
Last visited
-
Days Won
20
Posts posted by steffenmand
-
-
Fixed long time ago with the non public beta
http://dl.covecube.com/CloudDriveWindows/beta/download/?C=M;O=D
-
Got time to do it now.
Works better, however a lot of threads got "Internal Error".
While i was reading it was prefetching fine, but when i stopped it seemed to stop prefetching and ended up doing the dismount thing again with some prefetching mb still in queue.
Uploaded logs
After remount it started fine again as no prefetching mb were in queue. Have not had time to test if the file is corrupt yet
-
I have noticed with build .680 that my response times are between 2,500ms and 6,500ms. I dont know how much of an effect this has on things but I do know that with some of the older builds i was getting response times around 100ms.
Got the same thing but as he says it can be a lot of debugging stuff.
With the version that failed i got 5ms response times, so they can get really fast when they start to optimize for that. i got 3-4x the speeds with that low response time so it will make a difference
-
Will test tomorrow - will hope for a fix so i can upload and use data at the same time :-D will report back, also with thr logs if it doesnt work
-
Are you offering?
Better question, you know of a good, cheap VPS that offers unlimited gigabit networking, and Windows OS's?
Since you were planning for a VPS or dedicated server already, you could set up a VPN on it. That way, you could VPN in, add content to the drive (via a share, maybe) and then disconnect.
You can use a hetzner server www.hetzner.de. They are dedicated servers where you can get windows on the box - aren't that expensive - it all depends on the box
-
Upload stalls while copying to the drive. That's fine. But download is not possible during copy.
However when it finishes and the upload threads begin, no download threads are able to run (beside uploade verification). They will simply fail and end up causing unmount
-
Thanks for the reply...guess i will have to find another solution for my cloud pla
Just host in the cloud and get a server to run the plex server
-
I will do new logs :-)
Version: .672
Reproduce: Just copy stuff to the drive. As soon as upload appears threads stop and any attempt to download will give errors and up unmounting the drive
System specs: i7-6300, 32gb ddr4 ram, ssd drive
-
Im on the latest build. All uploads will in general freeze threads and it is easily reproducible on my servers. After the copy is done, upload threads will start along with upload verification.
If i try to load files while i have upload queued i would get the "could not download" error and it would pretty quickly unmount. when it unmounts the uploading data would be corrupt as some chunks are not properly uploaded. as i dont know which files are fine i have to reupload everything, which was just copied to the drive.
-
I understand that they are alpha builds :-) just noticed the huge change in response time which is a bottleneck in performance. If the response time was as good as i saw, then 20 mb would fully utilize my bandwidth and you could fully ignore the bigger chunks request as 1 gbit would be completely used with such a fast responsetime. however glad to hear that it will get better for release :-).
-
1000/1000 here :-) you just mentioned that netdrive gave you 4 mbit download
-
Hi i just tried .670 yesterday where i noticed that i got 5 ms response time on chunks. however uploads would fail at a point due to a number having to be positive.
In the new .672 this has been fixed, but my response time from .647 - .672 has growth from 4000ms to 10000ms. as .670 showed EXTREME fast response times i was wondering if you are doing stuff which delays the response? Back in the really early days i started with 400ms which now have increased to 10000ms giving less speed due to wait time.
Is there anything that can be done to eliminate all this extra response time as .670 obviously is bypassing some stuff and giving 5ms?
-
depends on the speed you get and more. i get great speeds so i got 20 mb chunks and 20 mb minimal download size.
if you get around 4 mbit you should most likely use less. try to make a few different drives and test various sizes to find your perfect fit
-
You will get way better speeds with stablebit as it is threaded and devided into chunks. that way you can dowbload up to 20 pieces at a time and in theory get 20x4 mbit on the download (or maybe more). As an extra benefit you get your files encrypted if you want, so they wont know what you are hosting :-)
I stream video just fine using stablebit - just make sure you have upload verification turned on.
You can always attach it on another computer.
Plex currently just takes a loooooooong time to index in for instance plex until they get an improved pinning engine in that can save the data we need locally
Btw! remember to use the latest beta build:
http://dl.covecube.com/CloudDriveWindows/beta/download/?C=M;O=Di recommend .667 as it seems stable right now. these new betas have huge improvements to the public one :-) - call it a benefit from being on the forums and giving them input.
-
you can turn upload off in the disk options! then just remove the tick when you are using the drive
-
Why do you prefetch that much? it will continue to prefetch more as you read. i think the delay is because it is getting those first 5 gb
i got like 400 mb at 160 sec timeout which works fine for streaming video files and more
-
would love this as well - however i think there is a technical aspect which makes this hard
-
Uploaded memory dump and logs from while it was uploading to the drive and all threads being frozen.
-
set upload threads to 0
-
Today this error resulted in a "The specified file found"not be found" leaving the drive frozen. this happened if the auto unmount happened during an upload.
ps. logs coming! gonna make a new test drive and force this behaviour on it multiple times :-)
-
Download seems limited, feels like they get throttled. Upload however is back at 974 mbps Download caps around 400 mbps wether it is 20 threads or 5
possible to get the same size chunks on google ? :-)
-
I noticed something awesome with Amazon Cloud Drive.... 100 MB chunks!! Woop woop! Look forward to testing some various chunk sizes to find a way to fully utilize my speed!
Do anyone know what the Amazon Developer Speed Rates are ? They must be limited to something -
When i got stuff pending in upload, it is impossible to download data. It seems as if it is totally blocked, but logs doesn't show anything but failed to download. I'm pretty sure that even with a high number in CloudFsDisk_MaximumConsecutiveIoFailures, this will fail rather quickly, as it fails during the entire upload. Same happens as upload builds up while copying to the drive - then no threads (upload or download) are able to run.
While i like the new unmount feature, it does corrupt uploads if it unmounts during an upload. Most likely because either threads were cancelled and marked as upload or simply because upload verification is not able to run - maybe even something else.
I'm using a SSD drive for the drives and it is not anywhere near maxed in speeds or capacity.
I'll post logs - but as mentioned i don't think you can read a lot.
-
Hi
I have previously mentioned this issur but will make a thread for it
Everytime i upload my files are not able to download in any way. with the new unmount on 3 download fails the drive will then end up unmounting - when this happens the current upload gets corrupt as it seems some chunks gets forgotten.
so
#1 Upload blocks for download
#2 Download while uploading causes the 3x download error and causes unmount leaving current upload corrupt
Currently i have to make sure my upload happens when i dont expect to use files for a while (400gb upload sizes)
would be great to be able to upload while also loaading files at the same time
Google Drive: Cant Upload, 'The requested mime type change is forbidden'
in General
Posted
.682 is working fine for me and its the newest. you can read the changes.txt whenever you see new builds to see if you want to test the new stuff out.
their rule though is that you should always be two numbered versions behind according to the changes.txt if you want a guarantee everything works.
They are really listening to the community and using our input to improve the product, which has become quite amazing. Personally i cant wait to see the final result they end up with