qBit does delete the file from my physical drive (direct attached storage, raid5). But won’t update the free space in the WebUI. The discrepency is over 1TB, so I’d like to address this if someone can help me.

Some info:

  • qBit v.5.0.1, docker, from linuxserver.io
  • Ubuntu 24.04
  • Automatic Management Mode is checked
  • Torrent content removing mode: Delete files permanently
  • renegadespork
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 hours ago

    I have this issue too, and I figured out a workaround. Deleting the files manually via rm frees up space. Deleting files via qBittorrent via UI or automatically does not.

    Turns out the files were just being moved to a “.Trash-UID” (where UID is the UID of the container) folder in the /downloads directory (or wherever that folder is mapped to on your host). Clearing that out freed up the space.

    I suspect this is a bug where the “Delete files permanently” setting is not being respected. You might want to set up a cron job to delete that folder periodically in the meantime.

  • Brickfrog@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    1 day ago

    Has it been happening since qBittorrent 5.x ? Only reason I ask is that 5.0 did introduce a new feature per https://www.qbittorrent.org/news

    FEATURE: Allow to move content files to Trash instead of deleting them (glassez)

    Maybe double-check the qBittorrent settings and verify that isn’t somehow enabled? I’m not on on that version yet so can’t be sure how that new feature works or is configured.

    If it’s not that then I suspect the other comments are right e.g. a hardlinked file elsewhere would defintiely mean you need to delete all the hardlinks to actually free up space.

    • ReedReads@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 day ago

      Yeah, I thought about that too. It’s why I noted in the post that my files are set to delete and not be moved to the trash first. Those settings are in options/advanced.

  • lime!@feddit.nu
    link
    fedilink
    English
    arrow-up
    1
    ·
    18 hours ago

    i’ve seen something like this before, where the kernel holds the file handle open for the process so that it thinks the file is still there. i think it’s related to how the program closes the file but i don’t remember the details. restarting qbittorent will most likely fix it.

    • ReedReads@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 day ago

      I deleted .25 terabytes and it hasn’t changed at all. It used to increment up after every deletion, so this is new.

  • catloaf@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    Does it update if you refresh the page? You may just want to file a bug report.

    • ReedReads@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      It doesn’t. I rolled the version back to 4.6.7 and it didn’t help, so I moved it forward again. Restarted the container, then the stack, then the whole physical machine. Nothing so far. Yeah, maybe I’ll file a report on their page.

  • tkw8@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 day ago

    Have you tried deleting the docker config and starting with a fresh install?