starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Torrents getting deleted #9196

New issue

Closed

opened 2026-02-21 20:02:33 -05:00 by deekerman · 17 comments

deekerman commented

2026-02-21 20:02:33 -05:00

Owner

Originally created by @jpjenkins on GitHub (Oct 5, 2019).

Please provide the following information

qBittorrent version and Operating System

Currently 4.1.8 - win10

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

Closing qB often deletes the entire queue list AND data (MAJOR ISSUE)

What is the expected behavior

Closing and opening should not affect anything.

Steps to reproduce

Choose from the many issues that have been posted over the last 3 years.

Extra info(if any)

Whether it's windows/linux or closing qB or letting it autoclose on restart, often it deletes everything in the queue, it's not so bad if you're using public trackers and manage your torrents manually, but absolutely useless if you have private trackers and need to maintain ratio etc.

I use transmission now and only have qB installed to use the search engine, I've been burned too many times over the last couple of years. On different os's and machines.

There are numerous issues that have been posted here but none seem to be taken seriously, there is a modified file of qB v3.3 from sledgehammer on #6262 but that didn't solve the problem for me.

Is this problem being addressed? Has anyone worked out what the issue is? I'm here out of love.

Originally created by @jpjenkins on GitHub (Oct 5, 2019). **Please provide the following information** ### qBittorrent version and Operating System Currently 4.1.8 - win10 ### If on linux, libtorrent-rasterbar and Qt version (type here) ### What is the problem Closing qB often deletes the entire queue list AND data (**MAJOR ISSUE**) ### What is the expected behavior Closing and opening should not affect anything. ### Steps to reproduce Choose from the many issues that have been posted over the last 3 years. ### Extra info(if any) Whether it's windows/linux or closing qB or letting it autoclose on restart, often it deletes everything in the queue, it's not so bad if you're using public trackers and manage your torrents manually, but absolutely useless if you have private trackers and need to maintain ratio etc. I use transmission now and only have qB installed to use the search engine, I've been burned too many times over the last couple of years. On different os's and machines. There are numerous issues that have been posted here but none seem to be taken seriously, there is a modified file of qB v3.3 from sledgehammer on #6262 but that didn't solve the problem for me. Is this problem being addressed? Has anyone worked out what the issue is? I'm here out of love.

deekerman

2026-02-21 20:02:33 -05:00

closed this issue
added the
Data loss
label

deekerman commented

2026-02-21 20:02:38 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Oct 7, 2019):

OFF: Used qBittorrent on Windows, Linux, BSD. Servers, NAS, VPS, mini computers, desktop computers, laptops. A dozen each. Used it on NTFS, ZFS, Btrfs, ext3, ext4, XFS, JFS, UFS. Had data loss only once about 2 weeks ago, lost my active torrents. Because I crashed Windows due to a bad OC setup. In 10 years, I really do not consider that bad and it was my own 100% fault. I guess there is always a step further in terms of stability, but it's really not that bad.

I believe there must be some other issues in the background at OP for having data loss so often.
Maybe OP has a HDD cache issue or a BIOS bug, or something. It can be worked around by setting Windows to disable write caching.

Go into Device Manager, Disk Drives, pick the affected drive (in this case I guess it's your boot drive), right click, Properties, Policies tab, and toggle "Enable write caching on the device" OFF.

Ps.: I have only lost session data and nothing else. That 1 I experienced. Data has never been lost in any way, shape or form.

@Balls0fSteel commented on GitHub (Oct 7, 2019): OFF: Used qBittorrent on Windows, Linux, BSD. Servers, NAS, VPS, mini computers, desktop computers, laptops. A dozen each. Used it on NTFS, ZFS, Btrfs, ext3, ext4, XFS, JFS, UFS. Had data loss only **once** about 2 weeks ago, lost my active torrents. Because I crashed Windows due to a bad OC setup. In 10 years, I really do not consider that bad and it was my own 100% fault. I guess there is always a step further in terms of stability, but it's really **not that bad.** I believe there must be some other issues in the background at OP for having data loss so often. Maybe OP has a HDD cache issue or a BIOS bug, or something. It can be worked around by setting Windows to disable write caching. Go into Device Manager, Disk Drives, pick the affected drive (in this case I guess it's your boot drive), right click, Properties, Policies tab, and toggle "Enable write caching on the device" OFF. **Ps.: I have only lost session data and nothing else. That 1 I experienced. Data has never been lost in any way, shape or form.**

deekerman commented

2026-02-21 20:02:38 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Oct 7, 2019):

15 Open Issues inclusive of this one on Data loss (dating back to furthest - 2012)
https://github.com/qbittorrent/qBittorrent/labels/Data%20loss

There are issues that are not user related....

@xavier2k6 commented on GitHub (Oct 7, 2019): 15 Open Issues inclusive of this one on Data loss (dating back to furthest - 2012) https://github.com/qbittorrent/qBittorrent/labels/Data%20loss There are issues that are not user related....

deekerman commented

2026-02-21 20:02:38 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Oct 7, 2019):

@xavier2k6

https://github.com/qbittorrent/qBittorrent/issues/7397
PEBKAC

https://github.com/qbittorrent/qBittorrent/issues/7146
NOT A BUG

@Balls0fSteel commented on GitHub (Oct 7, 2019): @xavier2k6 https://github.com/qbittorrent/qBittorrent/issues/7397 PEBKAC https://github.com/qbittorrent/qBittorrent/issues/7146 NOT A BUG

deekerman commented

2026-02-21 20:02:38 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Oct 7, 2019):

I am not the project lead, I am just saying.

There are millions of users out there. There is only 15 (now 14 since 1 was already pebkac), minus maybe half that are actually data losses. As you can see, some are just how libtorrent is made to behave through qBittorrent. Ie.: it is NOT DATA LOSS.

My whole point is: Don't cry wolf.

There is no plaguing, huge data bug lurking in the background just to erase all your torrents and data. It doesn't work like that. Yes, there might be an edge case out there among the millions. No software is perfect, and no one on this planet will ever be able to write a software and test it out on all the OS and hardware and situations.

@Balls0fSteel commented on GitHub (Oct 7, 2019): I am not the project lead, I am just saying. There are millions of users out there. There is *only* 15 (now 14 since 1 was already pebkac), minus maybe half that are actually data losses. As you can see, some are just how libtorrent is made to behave through qBittorrent. Ie.: it is **NOT DATA LOSS.** My whole point is: Don't cry wolf. There is no plaguing, huge data bug lurking in the background just to erase all your torrents and data. It doesn't work like that. Yes, there might be an edge case out there among the millions. No software is perfect, and no one on this planet will ever be able to write a software and test it out on all the OS and hardware and situations.

deekerman commented

2026-02-21 20:02:38 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Oct 7, 2019):

@Balls0fSteel I totally agree with you especially part about crying wolf!!, I was just pointing out as well not all are user error & some are as you pointed out not a bug etc.

But you can also see & agree/disagree that when someone looks at the data loss label as well as other labelled issues/time frames - can jump to conclusions...whether right or wrong.

Few issues have been opened up lately about project management relating to issues tracker etc which are basically duplicates of previous issues or may have been new ideas but could have been easily added to any one of the previous issues without having to open up a new one & increasing the issue count even further.

@jpjenkins I think this issue should be closed as it seems more of a rant/friendly advice/suggestion than an actual issue, if you do have an actual reproducable issue then please feel free to create an issue for that.

Also, remember that the dev's are actual volunteers doing this work on their own spare time, even those trawling through 2000+ issues labelling/closing etc.

So big peace & love to them!.

@xavier2k6 commented on GitHub (Oct 7, 2019): @Balls0fSteel I totally agree with you especially part about crying wolf!!, I was just pointing out as well not all are user error & some are as you pointed out not a bug etc. But you can also see & agree/disagree that when someone looks at the data loss label as well as other labelled issues/time frames - can jump to conclusions...whether right or wrong. Few issues have been opened up lately about project management relating to issues tracker etc which are basically duplicates of previous issues or may have been new ideas but could have been easily added to any one of the previous issues without having to open up a new one & increasing the issue count even further. @jpjenkins I think this issue should be closed as it seems more of a rant/friendly advice/suggestion than an actual issue, if you do have an actual reproducable issue then please feel free to create an issue for that. Also, remember that the dev's are actual volunteers doing this work on their own spare time, even those trawling through 2000+ issues labelling/closing etc. So big peace & love to them!.

deekerman commented

2026-02-21 20:02:38 -05:00

Author

Owner

@jpjenkins commented on GitHub (Oct 8, 2019):

So I decided to give it another try, some folk in forums swear by the v3.2.3. Alas, after 2 days it has now crashed, no data loss this time but all my torrents have gone. I noticed in the crash log that it says I'm using libtorrent v1.0.3. I checked it out and that's quite an old version, although I don't know if that's linked to qbittorrent v3. Do you think this is a possible reason? V1.3 is out now, I can't figure out how to upgrade though.

I'm at a loss, people talk about the resume files messing up etc. but I don't know. All I know is it keeps happening, for 2 years, over multiple devices and installs.

Can someone help get these torrents back up and running?

@jpjenkins commented on GitHub (Oct 8, 2019): So I decided to give it another try, some folk in forums swear by the v3.2.3. Alas, after 2 days it has now crashed, no data loss this time but all my torrents have gone. I noticed in the crash log that it says I'm using libtorrent v1.0.3. I checked it out and that's quite an old version, although I don't know if that's linked to qbittorrent v3. Do you think this is a possible reason? V1.3 is out now, I can't figure out how to upgrade though. I'm at a loss, people talk about the resume files messing up etc. but I don't know. All I know is it keeps happening, for 2 years, over multiple devices and installs. Can someone help get these torrents back up and running?

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@jpjenkins commented on GitHub (Oct 8, 2019):

Also, there are no torrents in C:\Users<username>\AppData\Local\qBittorrent and there's nothing important in the logs.

@jpjenkins commented on GitHub (Oct 8, 2019): Also, there are no torrents in C:\Users\<username>\AppData\Local\qBittorrent and there's nothing important in the logs.

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@jpjenkins commented on GitHub (Oct 8, 2019):

Does that mean everything's gone? I'd appreciate if someone with a bit more experience could let me know, thanks.

@jpjenkins commented on GitHub (Oct 8, 2019): Does that mean everything's gone? I'd appreciate if someone with a bit more experience could let me know, thanks.

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Oct 9, 2019):

Using the older versions have 0 additional benefit. In fact, you just have more bugs there.
I've been using the new versions without any problem whatsoever.
The older versions kept torrents, settings at a different location.

There is actually a big rule to any upgrade/downgrade... "backup your settings".... :/

@Balls0fSteel commented on GitHub (Oct 9, 2019): - Using the older versions have 0 additional benefit. In fact, you just have more bugs there. - I've been using the new versions without any problem whatsoever. - The older versions kept torrents, settings at a different location. There is actually a big rule to any upgrade/downgrade... "backup your settings".... :/

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@Mike-EE commented on GitHub (Oct 9, 2019):

@jpjenkins

Can you describe the architecture of your system and your download workflow in more detail?

@Mike-EE commented on GitHub (Oct 9, 2019): @jpjenkins Can you describe the architecture of your system and your download workflow in more detail?

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@NotTsunami commented on GitHub (Oct 11, 2019):

Starting to sound like PEBKAC to me...

@NotTsunami commented on GitHub (Oct 11, 2019): Starting to sound like PEBKAC to me...

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Oct 12, 2019):

Starting to sound like PEBKAC to me...

Just like 90% of the tickets, haha... such is life.

@Balls0fSteel commented on GitHub (Oct 12, 2019): > > > Starting to sound like PEBKAC to me... Just like 90% of the tickets, haha... such is life.

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@ChaosOrdeal commented on GitHub (Oct 18, 2019):

The death of most applications begins when its devs stop taking its users seriously.

@ChaosOrdeal commented on GitHub (Oct 18, 2019): The death of most applications begins when its devs stop taking its users seriously.

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@Mike-EE commented on GitHub (Oct 18, 2019):

The death of most applications begins when its devs stop taking its users seriously.

That's not, most fortunately, what's happening in this thread. How are the devs supposed to root-cause and address, if needed, issues in the code in the absence of any relevant data? "It's been going on for three years" isn't the kind of information that any programmer would need to investigate and fix a bug, assuming it even existed. All we know is that the OP is running 4.1.8 on a version of MS Windows 10...and that's it.

@Mike-EE commented on GitHub (Oct 18, 2019): > The death of most applications begins when its devs stop taking its users seriously. That's not, most fortunately, what's happening in this thread. How are the devs supposed to root-cause and address, if needed, issues in the code in the absence of any relevant data? "It's been going on for three years" isn't the kind of information that any programmer would need to investigate and fix a bug, assuming it even existed. All we know is that the OP is running 4.1.8 on a version of MS Windows 10...and that's it.

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Oct 19, 2019):

Yea these threads are pretty pointless, I'll just close it. Sorry folks.
Bugs are not ignored, but data removal bug is... is just straight impossible.

@Balls0fSteel commented on GitHub (Oct 19, 2019): Yea these threads are pretty pointless, I'll just close it. Sorry folks. Bugs are not ignored, but data removal bug is... is just straight impossible.

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jan 3, 2020):

Data removal bug confirmed by sledgehammer999 on May 29, 2018:
https://github.com/qbittorrent/qBittorrent/pull/9007

glassez commented:
"It is a very hateful situation, when hotfixes "rot" in the master for several months while the bugtracker is filled with duplicate issues!"

@Seeker2 commented on GitHub (Jan 3, 2020): Data removal bug confirmed by sledgehammer999 on May 29, 2018: https://github.com/qbittorrent/qBittorrent/pull/9007 glassez commented: "It is a very hateful situation, when hotfixes "rot" in the master for several months while the bugtracker is filled with duplicate issues!"

deekerman commented

2026-02-21 20:02:39 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (May 4, 2020):

This could be PEBCAK, but not enough relevant data was provided that could point to a problem in qBittorrent anyway. Plus the version used in the original report is too old by now anyway. There have been many changes in the core logic since. Please open a new issue if you have problems with the latest version.

@FranciscoPombal commented on GitHub (May 4, 2020): This could be PEBCAK, but not enough relevant data was provided that could point to a problem in qBittorrent anyway. Plus the version used in the original report is too old by now anyway. There have been many changes in the core logic since. Please open a new issue if you have problems with the latest version.