Deluge forgot new names of renamed folders after restart, if such folder wasn't available while deluged launch

[RussianNeuroMancer]

Looks like I have combination of two issues here: #605 and #1211.

In my case deluged get access to storage (just Linux with NFS server) with downloaded files via NFSv4. After restarting VM with deluged (deluged start is delayed for 120 seconds by upstart script, but this doesn't help) is probably trying to open too many files and fail - in result deluged starting to redownload around 70-80 torrents (it's 100% reproducible, but I can't find any related error messages in deluged logs, nor in VM syslog, nor in storage syslog). Moreover torrents that include renamed folder begin redownloaded with old folder name, that written inside torrent.

Please let me know, if I need to provide additional information.

[Cas]

Sounds like you are not shutting down deluged properly, please check the logs.

[RussianNeuroMancer]

Yes, I think about that too, so two last times I shutdown deluged using File > Quit & Shutdown Daemon. Unfortunately this doesn't help - issue still reproducible.

[Cas]

Are you certain that deluged shutdown properly? You need to verify with debug logging that the state file is being saved.

Also are you sure that the NFS mount is live before starting deluged? To rule out issues with the upstart script, you should start and stop deluged manually.

What version of libtorrent are you using?

[RussianNeuroMancer]

Are you certain that deluged shutdown properly? You need to verify with debug logging that the state file is being saved.

You are right. I tried to File > Quit & Shutdown Daemon again now, and even with warning loglevel I found this error message:

[WARNING ] 07:00:31 torrentmanager:774 Error trying to save fastresume file

After investigation I found that after moving deluged from root to regular user some time ago, I forgot to change permissions for some Deluge configuration files. Yes, torrents.fastresume was one of that files. After fixing torrents.fastresume permissions issue seems like no longer reproducible. Sorry for taking your time.