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
When deleting the torrent via the webUI, the pop-up box asks "Also delete the content files" is checked. Then the torrent and the files are deleted from the drive successfully. However, the "Free Space" number at the bottom of the UI will not update to reflect the increased free space. After a couple of torrent and file deletions, this has led to an over 1.5TB disparity between the actual free space and the qBit indicator at the bottom. See attached picture.
Expected Behavior
After deleting torrent and the related files, the "Free Space" indicator at the bottom of the webUI should increment up to reflect the newly freed up space. This is how linuxserver-qbit has always behaved prior to the 5.0.x upgrade (rolling it back did not revert the behavior however).
1. Host machine is ubuntu 24.04, docker-ce, storage is a QNAP DAS, 18TB Ironwolf drives, raid5.
2. Docker Engine Community v.27.3.1; API v.1.47
3. Portainer Community Edition 2.21.4
Is there an existing issue for this?
Current Behavior
When deleting the torrent via the webUI, the pop-up box asks "Also delete the content files" is checked. Then the torrent and the files are deleted from the drive successfully. However, the "Free Space" number at the bottom of the UI will not update to reflect the increased free space. After a couple of torrent and file deletions, this has led to an over 1.5TB disparity between the actual free space and the qBit indicator at the bottom. See attached picture.
Expected Behavior
After deleting torrent and the related files, the "Free Space" indicator at the bottom of the webUI should increment up to reflect the newly freed up space. This is how linuxserver-qbit has always behaved prior to the 5.0.x upgrade (rolling it back did not revert the behavior however).
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: