Search the Community
Showing results for tags 'box'.
Found 4 results
Hi all, Been experimenting and I think I found a bug, however, I did not want to do anything until I ran it by the community. I have signed up for a Free BOX.com drive. You get 10GB of space. What they did not tell you, is it seems you have less than that. I took a guess that they used hard drive manufacturers 10Gb (not 10gb) and it really was 9.7GB (there abouts). I found this by using this drive in a Drive Pool. The pool got saturated and that drive had over 9.7GB of data. That is, the drive was over 90% full. As Cloud Drive was trying to upload, it seemed to get stuck in a loop. After I noticed that this ONE drive was taking ALL my upload bandwidth, I hit PAUSE though the new PAUSE button. I validated that the settings changed (manage drive -> Performance -> Uploads UNTICKED). I also tried to use the "All drives PAUSE" under the pulldown (upper right Gear). Nothing I did could stop the upload from happening. I was sure this was happening as pulling the ethernet cable from the VM seemed to stop the upload (from the upload speed value being shown). After I plugged the ethernet back in, and a few hours later (I honestly do not know how long it was), I logged back into the machine and looked. I had a message in the message ticker that stated the drive was FULL and the upload attempt failed 260 times. EEEK! I also saw at least 1 other box drive listed in the log. I then tried to STOP and RESTART the Cloud Drive Process. This only seemed to anger other drives (now they had GB of data that was out of sync - this was being addressed in a Cloud Drive thread regarding rebooting and seemingly getting this error, which was brought to a conclusion with a TR/SR being submitted, so I did not bother...well bothering anyone about it). OK, all that aside, this drive was NOT going to stop trying to upload. I then tried a reboot. Still, no change. For a while, I just TURNED it's speed WAY down. That let other drives "catch back up" from the service stop and the reboot. At this point, I now think I discovered the issue. I changed a few settings on Drive Pool to fill to 80% as best it can, instead of 90% (just to be safe). I also mapped my box accounts to drive letters. Then MOVED an appropriate amount of data off to let me use the resize feature and set to 9.7GB. It seems just doing the move has made cloud drive happy and EACH drive that was STUCK like this has STOPPED trying to upload. I have only tested this with box (hence the post here). It might be with all - however there was a pretty long check when I SETUP the Google drives. If I put in a value that was too large, the original drive creation would fail. I would think this is the same with BOX? I am on the latest beta 22.214.171.1243 So, has anyone else seen this? Any tips? Is this just BOX? Thanks!
I have been testing several providers (Google Drive, Drop Box and Box.com). I am curious if anyone else here has been testing Box.com and their results with uploading files. I noticed with Google and Dropbox i can pretty much max out my upload connection (gigabit connection), 700-1100 mbps. and this is with just 5 upload threads. With box.com i see to get a different story with uploading only able to max about 50-70 mbps. Yes i have adjusted the upload threads and still no difference and upload bandwidth throttle isn't on. Box.com claims they do not throttle. So is anyone else here having slow uploads with them? If it helps i am uploading from the UK area. I have a feeling this is probably more of an issue with Box.com and their servers.
Hey CoveCube. I was looking into your neat software but recently ran into a really scary issue. Right now i have moved more than 1.8TB to BOX. The issue is that i can't detach the disk. It just says "Incorrect function". What the F* to do about that kind of error?