Sharing files with a Windows torrent client?

23Skidoo · Post by **23Skidoo** » Tue Dec 18, 2007 2:46 am

I have a problem using Deluge together with uTorrent - every time I start Deluge after I've ran uTorrent(under Windows), it thinks that my files(which I share between the clients) have changed and goes on to re-check the hash. It is very annoying. Another problem is that Deluge doesn't seem to remember the hash check progress - i.e. if I close Deluge while the check is going on, it starts hash-checking from the beginning when I run it again.

I'm using Deluge 0.5.7.1 and keep my files on a ntfs-3g partition.

markybob · Post by **markybob** » Tue Dec 18, 2007 3:12 am

23Skidoo wrote:I have a problem using Deluge together with uTorrent - every time I start Deluge after I've ran uTorrent(under Windows), it thinks that my files(which I share between the clients) have changed and goes on to re-check the hash. It is very annoying. Another problem is that Deluge doesn't seem to remember the hash check progress - i.e. if I close Deluge while the check is going on, it starts hash-checking from the beginning when I run it again.

I'm using Deluge 0.5.7.1 and keep my files on a ntfs-3g partition.

that's because utorrent changes the modified time of the file, so deluge notices that it's different. and yes, you need to let it finish the hash check before closing for it to remember. how can you remember half a check? it's very impractical

23Skidoo · Post by **23Skidoo** » Tue Dec 18, 2007 6:25 am

Thanks for your answer,

markybob wrote:that's because utorrent changes the modified time of the file, so deluge notices that it's different.

Actually, in this case utorrent changes only the "Time accessed", not the "Time modified". That's what I see in Windows properties dialog.

markybob wrote:and yes, you need to let it finish the hash check before closing for it to remember. how can you remember half a check? it's very impractical

If some torrents have been fully checked, then there is no need to start checking the whole list from the beginning - it shouldn't be very hard for Deluge to remember that.

markybob · Post by **markybob** » Tue Dec 18, 2007 7:05 am

23Skidoo wrote: If some torrents have been fully checked, then there is no need to start checking the whole list from the beginning - it shouldn't be very hard for Deluge to remember that.

deluge writes its fastresume file on shutdown, but only if the torrent is in a stable state (iow, isnt being checked). if you're closing deluge, while it's not hash checking, then it shouldnt recheck on the next startup. is this what you're experiencing?

23Skidoo · Post by **23Skidoo** » Tue Dec 18, 2007 7:32 am

markybob wrote:
23Skidoo wrote: If some torrents have been fully checked, then there is no need to start checking the whole list from the beginning - it shouldn't be very hard for Deluge to remember that.
deluge writes its fastresume file on shutdown, but only if the torrent is in a stable state (iow, isnt being checked). if you're closing deluge, while it's not hash checking, then it shouldnt recheck on the next startup. is this what you're experiencing?

No, the problem is that Deluge re-checks _all_ torrents on the next startup, even if it checked most of them previously.

About the uTorrent issue, i noticed that _sometimes_ the re-checking is not performed, which seems very strange.

23Skidoo · Post by **23Skidoo** » Tue Jan 08, 2008 3:56 pm

Another observation: sometimes Deluge re-checks _some_ torrents on next startup even if I haven't booted into Windows since last time(so uTorrent had no chance to alter their modification time). And sometimes there is no re-check even after I've used uTorrent. Maybe this is a bug somewhere on a border between libtorrent/NTFS/ntfs-3g?

stanley · Post by **stanley** » Sat Jan 12, 2008 11:41 am

Before I close off deluge I will select all and pause, so the next time no checking will be done.

23Skidoo · Post by **23Skidoo** » Thu Jan 17, 2008 6:56 pm

Thanks, I'll try that, but it's only a palliative.

Another observation: sometimes Deluge fails to notice that I've deleted the downloaded files(manually) and keeps on "seeding"..even though there are no files to seed. And when it finally finds out that those files are missing, it begins downloading anew:-(... I would rather prefer if Deluge behaved like uTorrent, which marks completed-and-deleted-manually torrents as "broken" and doesn't waste your traffic/rating.

And yeah, like I said earlier, the inevitable once-in-a-while full rechecking does not depend on whether I have booted into Windows or not. I keep my files on an ntfs-3g partition and the only non-default plugin enabled is Blocklist Importer(btw, it would be really nice if you added ipfilter.dat support).

23Skidoo · Post by **23Skidoo** » Sat Jan 19, 2008 9:51 pm

The obligatory rechecking is still there with 0.5.8.1, though the situation seems to have improved somewhat - only one torrent is usually rechecked.

Sharing files with a Windows torrent client?

Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?

Re: Sharing files with a Windows torrent client?