Bug 40001 - Quota policy can not overwrite user specific quota
Quota policy can not overwrite user specific quota
Status: NEW
Product: UCS
Classification: Unclassified
Component: Quota
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks: 48000
  Show dependency treegraph
 
Reported: 2015-11-17 14:14 CET by Johannes Keiser
Modified: 2018-10-16 11:28 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Keiser univentionstaff 2015-11-17 14:14:38 CET
The checkbox "Reapply settings on every login" does not overwrite user specific quota on login. In the UMC module the soft and hard limit for Data size shows 0/0 but the user specific quota is still valid.
Comment 1 Jürn Brodersen univentionstaff 2015-12-17 14:34:58 CET
Every share can have its own quota policy even if why are on the same partition. The problem is that the quota can only be set on a partition and not per folder.

Currently this is solved by mixing all policies and manual set quota values together if they are on the same partition. In the end the smallest value is used.

Example:
policy1
10/20   30/40

policy2
5/30    35/38

already set values
8/10    40/50

In this example the new quota would be:
5/10    30/40

That means "Reapply settings on every login" only works for smaller values than the currently set values. Deactivating the quota with 0/0 is interpreted as a bigger value.

Workaround:
Delete the quota in the UMC quota module before applying a new policy with bigger quota values.
Comment 2 Jürn Brodersen univentionstaff 2018-10-16 10:14:44 CEST
Another Problem (or it might have been the actual problem here):

Shares without a quota policy are interpreted as 0/0/0/0 quotas and can replace an actual set quota policy. This depends in which order the policies are evaluated.

Workaround:
Ensure all shares on the devices have a quota policy set.