>>2706634>>2706635well well well, torrent anon here. There was something bothering me and I think I know the problem now. In disk the folder amounts to under 140GB, but the torrent size is like 600GB? (its possible it only occupies 140GB on disk, you can test that on the <1KB torrent files on the end of this post)
You see, torrents are made of pieces, and the automatic piece size chosen was 4MB. The problem here, is that this folder has lots of small files (<4MB) and this piece quantization makes it so they are transferred in 4MB, well... pieces. Which is pretty insane, I wish the "Auto" piece size actually worked; one would think the creator would notice the `piece amount` * `piece size` would far surpass the actual torrent file size, but alas...
There's also some files I should omit, but I didn't find a torrent creator that accepts regex file exclusions so I'm going to have to make a script to move things temporarily.
I'm working on a now torrent, which should be compatible with anyone who downloaded this one (i.e. seeders can replace the current one and keep seeding).
And split torrents.
>>2706632do you know which kind of formatting that drive has? Like NTFS, ext4, etc.
if this torrent doesn't work for you:
magnet:?xt=urn:btih:ec4899799b819350c41c6896a01ec2494f92f885&xt=urn:btmh:12202923c0520a37bc12c82a127dfe293536a2ad7f1c0a1e8d07b3147ca724d04703&dn=test
and this works.
magnet:?xt=urn:btih:53ba983c5e8dac95298f6f4de688db09825ebfe7&xt=urn:btmh:1220761533685811fb9474aab0f4ae36e28c06c0af08c9d948ea7b9bb0a3cce12071&dn=test_nolinks
I know exactly what the problem is and will try to deal with it in the next version.
They are just folders and text files,
* but the above has a link to another folder
* the pieces are 4MB, the folder contents are under 1KB, but since it has 5 or 6 pieces the torrent size comes out as something like 20MB instead of less than 1KB.
If somebody downloads this and ends up using less than 1KB of disk, then the actual torrent will use 140Gb
