File checking

[Menard]

Hi, here Deluge 2.0.3 on Linux Mint 20.2 NTFS Data partitions
I checked the md5 of 2 downloaded files only to have a basis, after having proceeded to a check by Deluge, they were then in "queued" or "paused" or "seeding" state, I don't know, and I moved them to another partition, after this I checked the md5 again after check by Deluge and they both changed

What is the "check" feature really if it can be allright even if the files are modified ?
What conclusion to pull ?

[Menard]

I am sorry I ve just control my data and it appears that I had a mistake reporting hashes at the good row in a calc sheet, and so when i checked another file I had the hash that was missing

But it could interesting to know what "check" means, what do this feature consist in for Deluge ?

[mhertz]

But it could interesting to know what "check" means, what do this feature consist in for Deluge ?

Deluge runs libtorrent's force_recheck():

Code: Select all

void force_recheck () const;
force_recheck puts the torrent back in a state where it assumes to have no resume data. All peers will be disconnected and the torrent will stop announcing to the tracker. The torrent will be added to the checking queue, and will be checked (all the files will be read and compared to the piece hashes). Once the check is complete, the torrent will start connecting to peers again, as normal. The torrent will be placed last in queue, i.e. its queue position will be the highest of all torrents in the session.

https://libtorrent.org/reference-Torren ... ce-recheck

In short, and relevant to your question, then all files in torrent are hash-checked though said option. They are too during download, and additionally after(libtorrent default), but you can rerun the full check here again.