AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Skip hash check9/1/2023 ![]() ![]() The second case is a bit niche, but I believe it is legitimate. There should be no need to hash the data again, it's just wasting CPU/Disk I/O. The odds of a bitflip in that next 30 seconds you take to add it to transmission should be nil. The first case is rather obvious, you just created that torrent, and now you're putting it into transmission. For transfering a known torrent from another BitTorrent client to Transmission, or for loading a known torrent after reinstallation of Transmission ![]() For cross-seeding known equivalent torrents between trackersģ. For loading a torrent into transmission after creating it with some utility like transmission-createĢ. There are three use cases where this would be extremely useful, and not at all a legitimate risk of sending bad data.ġ. ![]() To eliminate this step, this feature can skip hash check. However, hashing large files in low performance hard drive can take several hours and significantly reduce hard drive life. When you are the first seeder for a torrent or you already have the data from somewhere else, Transmission will normally have to hash-check all files even if you just created the torrent file from them and thus know that they are correct. ![]()
0 Comments
Read More
Leave a Reply. |