You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current method to save fastresume is flawed. It allows fastresume corruption pretty easily.
If you don't have adequate space to write the fastresume, it will just write 0 Kb fastresume files.
If you force close qBt when writing fastresumes, it will get corrupted with no backups left.
What is the expected behavior
Write with a different file name, like 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume.bak
and if it succeeds, then rename it to 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume
Or rename existing one to 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume.bak and then write new one 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume
I don't think anyone would mind to keep a backup of these 2-3 KiB files.
The text was updated successfully, but these errors were encountered:
If you don't have 'adequate space' on your system partition, you are having bigger issues, aren't you? qbt can't really do anything here (writing backups would double the required space and double IO load).
But yes, writing fastresume-files isn't perfect (likely to be forgotten when quitting qbt or left corrupted somehow/not reflecting actual status in older versions).
Please provide the following information
qBittorrent version and Operating System
4.2.5 Win10 (10.0.1xxxx)
What is the problem
Current method to save fastresume is flawed. It allows fastresume corruption pretty easily.
If you don't have adequate space to write the fastresume, it will just write 0 Kb fastresume files.
If you force close qBt when writing fastresumes, it will get corrupted with no backups left.
What is the expected behavior
Write with a different file name, like 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume.bak
and if it succeeds, then rename it to 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume
Or rename existing one to 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume.bak and then write new one 9c5b41bae44dcee11db256297a3058f8a6690a7b.fastresume
I don't think anyone would mind to keep a backup of these 2-3 KiB files.
The text was updated successfully, but these errors were encountered: