It should always be the max value set by the admin who created the account/usergroup
The max-quota changes
The same wrong value can be seen in the user-area of the settings
Nextcloud version:
13.0.4
Picture 1

Picture 2
(512GB is the value that the user is allowed to fill, as set by an admin)

Picture 3

GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/2017 (quota), https://github.com/nextcloud/server/issues/6450 (quota: unlimited value), https://github.com/nextcloud/server/issues/4572 (Wrong total quota limit with shared hosting), https://github.com/nextcloud/server/issues/6754 (Invalid quota value "0"), and https://github.com/nextcloud/server/issues/8050 (Quota issues ).
That is maybe because your server runs out of total space. We take as quota the minimum of "quota set by the admin" and "free space available + already stored files"
That could explain it, but which stored files? generally stored by the whole cloud, or by the user?
If it is the user, the value is still wrong because i would need less than 250Gb free serverspace, but i have more than that available.
Interestingly enough, if i reduce the max value for the user, the expected value shows up.
That could explain it, but which stored files? generally stored by the whole cloud, or by the user?
The ones of you. A little example:
So this is more an expected behavior than a bug.
Thank you for your clarification! I'll check if this adds up to my server, and then close the ticket.
It seems that this behavior does not work consistently.
My OS (ubuntu server 16.04) reports 600Gb used, 300Gb free.
This should result in the correct display of 512Gb, since the remaining 250Gb are smaller than the free space, so there is enough serverspace to store everything.
It seems my server was hiccuping. After changing (and changing the value back), only the assigned value was shown.
Also, would it make sense to indicate that an amount is missing from your assigned quota?
Something like this, with an tooltip that says there is not enough server space?

I tried something. Maybe this is something we want?

I tried something. Maybe this is something we want?
Not really, as the user can't do anything about it. And if the user can't do anything it doesn't make sense to show it to them. maybe the admin should get a warning.
Let's make a new issue for your proposal and how to trigger it. It is an enhancement of the admin view and might make sense.
What proposal do you mean exactly?
What proposal do you mean exactly?
To show somewhere that the storage limit is reached for some users (use the user with the biggest number of "quota - used space" and then check against the available space on the storage).
So, I use thin provisioning (lvm), which will pull from a pool with additional storage when low. But the amount of free space reported to the OS is less than the pool. Therefore, the users are actually shown less space available than there actually is. Need to figure out some way to show users the amount of space provisioned to them, regardless of the space "available" to the OS.
Most helpful comment
The ones of you. A little example:
So this is more an expected behavior than a bug.