Deluge not locking files while seeding.

[tdc]

Hi, i am running deluge 1.3.11 under Debian 8. I have thousands of torrents seeding and deluge doesn't keep a file lock on them. Sometimes I happen to move a file to organize it but since deluge doesn't lock it i am able to move it. That causes errors whenever that particular torrent is requested.

Is there any way of keeping the file locks on every single seeding torrent? Currently it only locks the files whenever they are accessed from hard drive.

[Shryp]

You can move the files through deluge by right clicking and selecting move storage.

You can download the ltconfig plugin and enable file locking.

[tdc]

I am aware that i can "Move Storage" from the console and gui. But like I said, I have thousands of torrents, some dating from 2013. There is no way I can remember all of those, but if the files are locked, i wont be able to accidently move them.

I installed the ltconfig plugin, restarted the deluge daemon. It still only locks files which are being read or written too. I tried rechecking a torrent to try to bring the file to be locked, but no luck.

[Shryp]

I installed the ltconfig plugin, restarted the deluge daemon. It still only locks files which are being read or written too. I tried rechecking a torrent to try to bring the file to be locked, but no luck.

Did you enable the lock_files option and then apply it? I don't use that option myself, so not sure exactly what it does or how it works.

From http://www.libtorrent.org/reference-Settings.html

lock_files
determines whether or not to lock files which libtorrent is downloading to or seeding from. This is implemented using fcntl(F_SETLK) on unix systems and by not passing in SHARE_READ and SHARE_WRITE on windows. This might prevent 3rd party processes from corrupting the files under libtorrent's feet.

[tdc]

Sorry totally forgot to mention I have activated lock_files in ltconfig from the gui client.

According to this about the f_setlk function : http://www.gnu.org/software/libc/manual ... Locks.html.
It should be doing exactly what I want.

I would expect the result of the following command that lists all locked files to show all the files being seeded.
lsof | grep "deluged"

All i get is the files which are active. Same as the ones shown in deluge if "info -s active". I have tried rechecking torrents to try to force them to lock. I can briefly see them being locked as they are checked. But as soon as they are "seeding" the lock goes away. Adding a new torrent does the same, only locks the file white its active.

[Shryp]

I have never used that option myself, but I have accidentally moved things around once or twice and caused deluge to crash, so maybe I should play with it. It might act different if you upgrade to a different version of libtorrent. 1.0.5 is the newest version and I am using that. Not sure if you have updated yours or not. The default that comes with deluge 1.3.11 is version 0.16.18. You can compile from source yourself, or there is a link to adding an ubuntu ppa repository somewhere. I think that will work on Debian.

http://www.libtorrent.org/

http://dev.deluge-torrent.org/wiki/Inst ... Repository

[tdc]

I have compiled and installed libtorrent 1.0.5.0 and verified it was using it with "deluged -v"

deluged: 1.3.11
libtorrent: 1.0.5.0

I get the same result. I am thinking that deluged doesn't actually ask for the file to be locked, and is probably independant of libtorrent. I think this will require a bug report/feature request