Puting a huge multipart torrent on multiple drives

[cayonara]

When you want to download just some files from a multi - file torrent

because all the files from that torrent would not fit on your selected hard drive,

it keeps disconnecting

(at the instant moment cache would have been written to disk)

and clearing all the downloaded data

ignoring the fact you have put the rest of the files to "don't download" state.

I think that is a bug, not feature - as reading from multiple disks when seeding is way much faster than reading from single disk..

[ciaobaby]

ignoring the fact you have put the rest of the files to "don't download" state.

Files flagged as "Don't Download" may still be downloaded completely

The actual data that makes up the file may be in several different "pieces" so some files will be completed simply because they "shared" a piece that had part of a file you did want.

Torrent clients only "understand" the metadata that tells them how the pieces fit together, There is no concept of 'files' and 'folders' it is just binary data that fits together to create "files" that the disk filing system can then "understand".

Disk filing systems work in similar way, a file that is larger than a "allocation unit" is 'fragmented' and spread over several units and may not be in contiguous disk sectors, this is why you have to 'defrag' your disks from time to time so the files are stored in contiguous sections. Although in a DFS files do not 'share' units, so a 1 byte file may be using 4k of disk space which is the default allocation unit of a disk larger than 32 Mb on a Windows 32 bit operating system.

[ciaobaby]

Whoops went on a bit of a "techy trip" there,

[cayonara]

Oh, thanks a lot for the clarifying answer, i was too lazy to explore the details of .torrent technology.. And for "techy trip"- enjoyed it indeed

Lets take a case scenario => torrent consists of 2 files: F, T, O (reference to Obesity gene lol); F is 4GB, T is 2GB and O is 1GB. An user would like to grab and share file F and O on her SSD drives that are mount-ed/subst-ed as F: and O:

On the one hand, i got the concept that as there are no "files", so there is no guarantee that when µTorrent would try to (check and reserve): F: for 4GB of space and O: for 1GB of free space there would be no guarantee that such amounts would be enough as some pieces could be located in Ts parts resulting in more space required

but (love the Game of Thrones line~= "Anything person says before but doesn't really matter as in most cases its just a try to ease up getting the other person agreeing with the part that follows after the but word ")

isn't there an easy way to get the real file size from metadata; and with real i mean file size + overhead generated by these linked piece part distribution? Because ability to set various locations for various files in a single torrent while choosing only a part of a torrent is a precious one imvho