It is quite tricky to clean that folder manually. There should be a system/dialog, which cleans the backup folder from broken/lost/forgotten fastresume and torrent files.Otherwise it is very difficult to restore them as all files in backup folder are named as hash. Then you know, which torrents should be fixed. Working fastresume files with damaged torrent files should still present in torrent list as a "broken job" similar to uTorrent jobs with lost torrent files.Then in case of damaged fastresume files - take next copy from backup. Fastresume files are relatively small and you can save several backups of them, for example, each period (modify that setting in "2" not to save on top, but also move older copy to backup) and keep archive of X copies. There should be some more clever automatic backup system added.They will be saved once more (if changed). You may backup at this stage, then start torrents again and stop again. Stopping the job saves it and it will not be lost or damaged in most of the cases. My exemplar was working for a day after shutdown, until I killed it. If you shutdown client with active torrents - it will never shutdown and will continue to work in background forever. If you have thousands of torrents you will end in endless loop of saving that files, QB saves them by about 10 files each second, so when the queue ends - it already starts from the beginning. If job changes it will save anyway, periodic saving just updates active FR files cyclically with same data. Disable periodic saving of resume data - first of all this is pointless.It is still fine in case you also follow "2". Then QB will shutdown in several seconds instead of several minutes, because if you shutdown the actively working client it is left in background saving fastresume files for changed jobs. Stop all torrents before shutdown/restart.This will help you to get more adequate behavior of QB, if you have thousands of torrents. I have some recommendations based on bad experience and lost days of work. And now have about 6300 (Ccleaner thing). And then after each crash or restart lost more and more. Reply to this email directly, view it on GitHub, or mute the thread. You are receiving this because you commented. I do see the torrent files, but some of the fastresume files are 0 bytes - any idea on how to recover? However, when I started up qBittorrent again - it only loaded 98 out of around 1000 torrents from before. I ran out of disk space - so I cleared up some old downloads. I was running qBittorrent inside a Docker container under Ubuntu 18.04. I haven’t found a solution no, in the end I just reloaded all torrent files, losing all of my statistics ☹ 10:48 AM - qBittorrent is trying to listen on any interface port: 8999 10:48 AM - HTTP User-Agent is 'qBittorrent v3.3.3' 10:48 AM - Local Peer Discovery support 10:48 AM - Options were saved successfully. 10:48 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433 10:48 AM - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433 10:48 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/8999 10:48 AM - qBittorrent is successfully listening on interface :: port: TCP/8999 10:48 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/8999 10:48 AM - System network status changed to OFFLINE 10:48 AM - System network status changed to ONLINE fastresume files there in addition to a session.lock file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |