Two issues regarding disk space

[Deny-DD]

Description

There are two issues here.

First, the reported total size is smaller than the reported free space.

Second, the application seems to calculate availability solely from df, whereas it should also account for user-level quotas from quota -u.

Free space on the filesystem is not equivalent to the space actually available to the current user.

Steps to reproduce

Nothing much. Observe the cards on the dashboard.

Environment

qui: 1.33

Log link

No response

Relevant logs

No response

Checklist

• I have searched existing discussions and issues
• I have checked the documentation

[github-actions[bot]]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Show free space that takes the disk quota of the user into account, next to or in place of the free space that qBittorrent reports.

Current behavior:
The two points in the report act as follows in the code:

1. Total Size is not disk capacity. On the dashboard instance card, "Total Size" is the sum of the sizes of all torrents on the instance, cross-seeds included. The tooltip on the label says this. It is not the size of the disk, so it can be smaller than Free Space. That is expected, not a bug.
2. Free Space comes from qBittorrent. qui does not run df or measure the disk. The card shows free_space_on_disk from the qBittorrent sync data without a change. qBittorrent measures the volume of its default save path, and that number ignores user and group quotas. On a host with a quota per user, the card can show much more space than the user can write.

Desired behavior:
When the user turns it on, the dashboard (and the torrent status bar, which shows the same value) can show space that respects the quota of the qBittorrent user: the smaller of the volume free space and the quota left (limit minus usage). The label makes clear which source the number comes from. When qui cannot read the quota (no local filesystem access, a remote instance, an OS without quota support, no quota set), it shows the qBittorrent value as now, with its current label.

Key interfaces:

• free_space_on_disk (qBittorrent /api/v2/sync/maindata server_state): the source today, stays the fallback.
• FreeSpaceSource (automations): already chooses between the qBittorrent value and a filesystem-backend path. A quota-aware source should reuse this concept, so the dashboard and the FREE_SPACE rules do not get two different ideas of free space.

Acceptance criteria:

• The dashboard and the status bar show which source a free-space value comes from.
• With a quota-aware source turned on and a user quota set, the shown value is no larger than the quota left.
• With no quota, or when qui cannot read it, the value equals free_space_on_disk.
• A failed quota read shows as unavailable or falls back. It never shows as zero.

Out of scope:

• Changing what "Total Size" measures.
• Running provider-specific commands to read usage.

Domain:

• Glossary terms: none in GLOSSARY.md for free space or quota (gap).
• ADRs: None.
• Owner: the free-space source selection that automations use today (FreeSpaceSource). The dashboard does not use it yet.

Related:

• Issue feat(automations): quota free-space source, allowance minus walked usage #2921: a quota free-space source for automations on shared seedboxes, where a provider allowance is enforced instead of a kernel quota. This request is for kernel user quotas (quota -u), and for the dashboard as well.
• Issue Use path-aware free space across qui #2599: path-aware free space across qui, including the dashboard source label.

Logs:

• None

Why a human: Feature scope is a maintainer call. Decide whether kernel quotas belong in the FreeSpaceSource work in issue #2921 / #2599, and how qui reads them when it does not run on the qBittorrent host.

[Deny-DD]

Furthermore, I see you’re preparing support for remote filesystems. Consider retrieving those values directly and providing a manual override for the available disk space on each instance.