I had downloaded 25% of a torrent, paused it, rebooted my system and "forced a check". The result is that Deluge now only sees 10% of the downloaded content. I had this happen a couple of weeks ago already, but it was after a power outage, so I blamed the problem on corrupted data (though it made no sense since I had put back backuped data from the day before). However, this time there had been no problems, and I did run a fsck, too. I do have a backup of when it was at 25%, before it continued downloading at 10% after the forced check. It seems that various files that were partially downloaded now show at 0%.
Any suggestions for how to proceed? I'd hate to lose several days of downloading. The Deluge version I'm using is 0.5.9.1, Ubuntu 8.04.
Is the downloaded data (full allocation) compatible with other BT clients? (If only to see if it's the data or Deluge).
Issue with "checking" -- half the data gone?
Re: Issue with "checking" -- half the data gone?
To answer my own question: The data is compatible with at least Transmission.
Transmission checked the data and says that 25% is downloaded (about 5.1 GB). Deluge's re-check says 10% and it sees only 2.1 GB (note that before the check/re-check, Deluge also had correct figures). Seems like it might be an issue with Deluge's checking/re-checking function?
Transmission checked the data and says that 25% is downloaded (about 5.1 GB). Deluge's re-check says 10% and it sees only 2.1 GB (note that before the check/re-check, Deluge also had correct figures). Seems like it might be an issue with Deluge's checking/re-checking function?
Re: Issue with "checking" -- half the data gone?
More on this: It seems that checking/rechecking simply skips every other 10%. It scans from 0 to 10%, skips directly to 20% and scans through to 30%, skips straight to 40%, etc. That is why it shows only half the size. Graphically, it looks like this:

This also happens in 0.5.8.9.
(I'll also say that Transmission is the pits. I hope this trouble if fixable.
)

This also happens in 0.5.8.9.
(I'll also say that Transmission is the pits. I hope this trouble if fixable.

Re: Issue with "checking" -- half the data gone?
It could be a .fastresume problem, as long as you have the data backed up to the 25% mark try deleting the .fastresume file and force recheck.
Or another idea would be to remove the torrent from deluge and re-add it since it would also recheck whats been downloaded so far.
And I think that graph bar is showing which file chunks have been downloaded and verified or something.
Or another idea would be to remove the torrent from deluge and re-add it since it would also recheck whats been downloaded so far.
And I think that graph bar is showing which file chunks have been downloaded and verified or something.
Re: Issue with "checking" -- half the data gone?
The file chunks had been evenly spread out. After rechecking, only half of them are recognized. The checking skips every other 10%, and it isn't even trying to read the tenth inbetween two tenths that it reads (I hope this makes sense). Also, this only seems to happen with torrents that consist of a larger number of files, i.e. various seasons of a TV series.
The data is definitely there and also properly handled by Transmission. I downloaded 4% more with Transmission, and Deluge sees 2% more.
I tried deleting the fastresume file, deleting all config files, reinstalling Deluge, deleting the data and putting back the backup, and I re-downloaded the torrent file.
The data is definitely there and also properly handled by Transmission. I downloaded 4% more with Transmission, and Deluge sees 2% more.
I tried deleting the fastresume file, deleting all config files, reinstalling Deluge, deleting the data and putting back the backup, and I re-downloaded the torrent file.
Re: Issue with "checking" -- half the data gone?
Dunno....never had to recheck anything in deluge after they fixed the random recheck issue....Deluge does have a tendency to not save/drop data downloaded though based on random (and seemingly benign) stimuli.
Re: Issue with "checking" -- half the data gone?
Happy to report that this appears to have been fixed in 0.5.9.2!
It checks properly now. For testing purposes, I went back to 0.5.9.1, and half the data was skipped again. So, seems to have been a bug that struck only if some conditions were met.
