Damn 1.02 rechecking torrents after reboot ((

[andar]

2 andar

Thanks for the answer.

Configs and fastresume-files are in /.config/deluge , right?
There is deluged.log. For all festresume files found strings:

[DEBUG ] 03:07:09 alertmanager:101 fastresume_rejected_alert: Numb3rs-2 fast resume rejected: file size for 'Numb3rs-2/numb3rs.s02e01.avi' was expected to be 377163776 bytes

There is many other interesting strings, so is it what you asked?

About allocation... I use russian language, so do you mean the reservation mode in prefs-->downloads? If so, I use full reservation for torrents as its recommended.

By the way, in addition to download progress deluge 1.0.4 don't save columns order and any visual changes that I do. Seems like deluge simply do not or can not store it because of security permissions or other reasons.

Maybe i should delete /.config/deluge at all to force its creation by 1.0.4?

Can you tell me how many bytes the file size was for Numb3rs-2/numb3rs.s02e01.avi'?

[Fimir]

2 andar

numb3rs.s02e01.avi 359,7 MB (377163776 bytes)

[Fimir]

2 andar

I've made some tests.

Added only one torrent (for aforesaid Numbers-2), it checked, seeded. Then I closed deluge manually, then reboot. After reboot seeding continues without recheck (all ok in deluged.log).
Then I just gone reboot without manual closing. After reboot torrent start rechecking, and there is a familiar string in deluged.log about expected file size.

Thus there is a bug in deluge shutdown. When system goes reboot deluge don't save torrents state. Maybe it just don't have enough time for that?

In addition, maybe this problem occurs because deluge 1.04 don't have manual parameter where fastresume files should be stored, while 0.5.9.3 have? So fastresume files are in /.config/deluge in homedirectory, while files and torrentfiles are in other partitions with different filesystems, and maybe unmout command done before deluge save torrents state? It's just an idea
Anyway with deluge 0.5.9.3 I store fastresume files in the same directory with .torrents and their files.

[dmx77bole]

I ve tried with 50 torents and didnt worked....
Guess what Im downloading again:)))))))))))

[andar]

2 andar

I've made some tests.

Added only one torrent (for aforesaid Numbers-2), it checked, seeded. Then I closed deluge manually, then reboot. After reboot seeding continues without recheck (all ok in deluged.log).
Then I just gone reboot without manual closing. After reboot torrent start rechecking, and there is a familiar string in deluged.log about expected file size.

Thus there is a bug in deluge shutdown. When system goes reboot deluge don't save torrents state. Maybe it just don't have enough time for that?

In addition, maybe this problem occurs because deluge 1.04 don't have manual parameter where fastresume files should be stored, while 0.5.9.3 have? So fastresume files are in /.config/deluge in homedirectory, while files and torrentfiles are in other partitions with different filesystems, and maybe unmout command done before deluge save torrents state? It's just an idea
Anyway with deluge 0.5.9.3 I store fastresume files in the same directory with .torrents and their files.

Yes, it could be that deluge doesn't get enough time to shutdown properly, since it needs to pause all torrents, request resume data from libtorrent and then write out the files. The strange thing is that Seeding torrents shouldn't really need to be rechecked since the filesize should not be changing, so it could be that you are modifying these files prior to restarting Deluge or perhaps the calculation of their filesize is not working properly with NTFS.

I would strongly suggest not using NTFS.

[dmx77bole]

Not using NTFS isnt a solution....
In my opinion we have 2 options ... 1 to change to the last version of deluge that didnt make problems or 2 to change the client (other then deluge)

[Fimir]

2 andar

NTFS denial is impossible at all. Though I work on Linux, I still use Windows for gaming purpose. CD-images for modern games that I download with torrent could only be started from Windows. If I change filesystem in partition where downloaded files stored to any other different from NTFS, my Windows simply won't see it.
So it's not an option.

Besides, there it no problem at all with deluge 0.5.9.3 from Ubuntu repos. So the problem is in new version.

I would very like to test the situation if fastresume files stored in the same directory with torrent files, but there is no manual setting for it. So what should I change in deluge configs and where they are? (deluge for Ubuntu 8.10 x86).

[Barm926]

1.2.0 (win) does it too
not for all files, but it does.
when shutdown manually and strart - all ok. when reboot machine, using windows command and starts after - some torrent starts "Checking..."
it looks like this torents were "active", when shutdown was started

OS: Win7 x86, FS: NTFS

Can't find neither "deluged.log" nor "deluge.log".
A have searched at ALL my disk drives, not only %APPDATA%\deluge\