Reference qbittorrent save path

qBittorrent container on media-server (CT 102) bind-mounts only two host paths: /opt/stacks/media/qbittorrent -> /config and /mnt/storage -> /mnt/storage. There is no /downloads bind mount, despite the qBit config historically referencing /downloads/. The real download tree is /mnt/storage/downloads (on /dev/sda, 24TB).

Trap: adding a torrent via the WebUI API with savepath=/downloads/... writes into the container's overlay (writable layer) on the 50GB CT root disk, not the big storage pool. A large download silently fills CT-102 root to 100%, which breaks Sonarr/Radarr SQLite writes (database or disk is full, HTTP 500 on every PUT/command). 2026-06-08: a 34GB Monk pack added with savepath=/downloads/monk-complete did exactly this; fix was delete the torrent+data and re-add with savepath=/mnt/storage/downloads/monk-complete.

Rule: any programmatic qBit torrents/add on media-server MUST use a path under /mnt/storage/. Never /downloads. Verify a new torrent's save_path after adding and confirm df -h / on the CT didn't jump.

CT-102 root was grown 50GB -> 66GB on 2026-06-08 (Finn pve VG had only 16GB free, so 125GB was not reachable). WebUI\LocalHostAuth=false, so the API is reachable without creds from inside the container. See also [[feedback_media_server_deploy_bind_mount]].

[Claude Code]