Torrenting about cloudfuse HOT 1 CLOSED

When you're running a download or a torrent, there are often multiple filesystem connections to the same file. For instance, I use jdownloader which downloads multiple pieces of a file from a single source (via multiple download connections).
Due to how it operates, cloudfuse is not well suited for such actions. Once a file exists in the cloudfuse mount point, after it is finished being written to, the file is then sent via http to Rackspace Cloud Files.

So this means if you have a torrent file that is being saved in bits, or in my case a file that is being saved in parts, this can cause a conflict with out cloudfuse actually functions.

It appears an additional factor may be how cloudfuse caches files that are stored in your mount point (as you don't have files physically stored there, they are just virtually represented by cloudfuse from the remote cloud files server).

Regardless, the better process is to do any partial file writing via normal disk (i.e. - physical storage), and once that is complete, move the file to your cloudfuse mount point.

Also, watch out for >5gb file sizes, as they will error. To handle those files properly, check out this link:
http://www.rackspace.com/knowledge_center/index.php/Does_Cloud_Files_support_large_file_transfer

from cloudfuse.