I’m trying to upload large file(1 TB) with split by 100mb. First time odrive stuck on 59 chunks(5.9GB), after that it keep consume bandwidth, but no new chunks added. Then I renamed this file, it’s started to uploading again and then stuck on 28 chunks. Same as before odrive keep consume a lot of bandwidth but no new chunks added. Restarting odrive/mac doesn’t help
Hi @drapl,
Can you send a diagnostic from the odrive tray menu while this is happening, please? Please also let me know what the name of the files/file is that is have the issue.
Since this is a very large file, there may be issues with the number of chunks allowed in a folder. Can you try something while we are going through this?
Move the file out of odrive, so it stops syncing
On Amazon Drive’s web interface, remove the partially uploaded IFS folders
I’m in the process of uploading a 300GB to Amazon Drive. I am seeing that some exceptions are hit during the upload that can cause the file to be put back into waiting or into not allowed for a time. But, it recovers and continues syncing after a little a delay. I am currently at 2,133 100MB segments.
The problem with hitting Amazon Drive exceptions is that continuing the upload on such a large file is expensive because odrive has to figure out where it left off, which means it needs to hash the file. Hashing a 1TB file will take quite a while during which it will look like nothing it happening. A single 1TB file is incredibly large.
We are looking at ways to optimize the handling of this, but this size of a file is really pushing the limits.
Just tryed build 6002 - same behavior. Eated 700mb of bandwidth and no one chunk was added(split size: 100mb). My region is South-East Asia. I think region of Amazon account is same
I am expecting that folder to be there along with many files inside.
I also see that Amazon is complaining about a duplicate name for one of the files in the package: 2f282b84e7e608d5852449ed940bfc51. This may be causing things to hang up. If you delete that file inside (from the Amazon Drive web client), I think it will continue on. I am not sure why that exception is happening. I will need to look into it.
Can you delete the 2f282b84e7e608d5852449ed940bfc51 file from the web client and then wait for odrive to try to sync the file again (after falling back into waiting), then send another diagnostic?
What is odd about this is that odrive should be seeing the contents of the xlarge folder, including the files it has already uploaded, and skipping them. The fact that it is not could mean that it isn’t getting the proper listing from Amazon, but I don’t know why that would be. In my own test against Amazon Drive, I resumed several times, with up to 3000 chunks, and it was able to pick up where it left off.