reverting to saved state for torrents to skip recheck...
Posted: Wed Feb 28, 2018 3:24 am
Before submitting to the wishlist of feature requests, I'd like to get your thoughts on this...
qbittorrent (and I'm sure other clients) doesn't always exit cleanly (or takes a _long_ time to do so, requiring killing it when you need to, say, reboot). This, of course, will trigger a recheck upon restart for most if not all downloading torrents, which can take a very long time.
Unless I'm missing something, I think it would be good to have the option for qb to revert to a recently saved state for downloading torrents and skip the recheck upon restart even when it detects a problem with the torrent (e.g. timestamp mismatch). Even if the state is saved only, say, once an hour, you would only be re-downloading at most an hour's worth of data, while avoiding quite a few hours of recheck. Now, in the case of filesystem corruption from a crashed system, this would not be a good idea, but that is much more rare than having to restart qb before it can exit cleanly.
What do you think?
While we're on the subject, I noticed both with 4.0.3. and 4.0.4 running on Win10 (at least) that even when I exit qb cleanly, on several occasions it reported in the log a mismatch of timestamps which triggered a recheck of most downloading torrents. I was using 3.X for months before 4.X and I don't recall that happening. That's what prompted this possible feature request. Anyone else experienced this?
qbittorrent (and I'm sure other clients) doesn't always exit cleanly (or takes a _long_ time to do so, requiring killing it when you need to, say, reboot). This, of course, will trigger a recheck upon restart for most if not all downloading torrents, which can take a very long time.
Unless I'm missing something, I think it would be good to have the option for qb to revert to a recently saved state for downloading torrents and skip the recheck upon restart even when it detects a problem with the torrent (e.g. timestamp mismatch). Even if the state is saved only, say, once an hour, you would only be re-downloading at most an hour's worth of data, while avoiding quite a few hours of recheck. Now, in the case of filesystem corruption from a crashed system, this would not be a good idea, but that is much more rare than having to restart qb before it can exit cleanly.
What do you think?
While we're on the subject, I noticed both with 4.0.3. and 4.0.4 running on Win10 (at least) that even when I exit qb cleanly, on several occasions it reported in the log a mismatch of timestamps which triggered a recheck of most downloading torrents. I was using 3.X for months before 4.X and I don't recall that happening. That's what prompted this possible feature request. Anyone else experienced this?