nextcloud / nextcloud/groupquota
Trashbin and versions retention policy not working
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 35
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
Hi,
What we are seeing is this:
a dedicated disk of 100GB for data, we added groupquota, all users are added to the group everyone, and this groups gets a 100GB quota.
You're not able to use 100% of the quota, that's no problem. The system reports the correct numbers in xxx used from yyy available.
The problem is, with trashbin and file version enabled. The cleanup policy isn't working.
if the drive is full or near full, Nextcloud doesn't expire the oldest entries in trashbin or versions folders of all users.
Is this a bug? or am I just missing a configurable item here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported setup with a 100GB group quota, trashbin enabled, and file versions enabled. Check whether cleanup occurs when the quota is full or nearly full, and document the configuration or behavior that explains whether the oldest trashbin and version entries are removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100