⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Currently the trash volume is not accounted for in the total available space for the package. A user can fill the trash exceeding quota multiple times and then, before the trash bin clear-job runs recover all files from trash and blow the quota.

Steps to reproduce

1. take a user account with a limited quota and "auto" settings for 'trashbin_retention_obligation'
2. fill up the trash by deleting files exceeding the quota
3. recover the files from the trash bin
4. observe the files are recovered and available quota is over-boarded.

Expected behavior

1. take a user account with a limited quota and "auto" settings for 'trashbin_retention_obligation'
2. fill up the trash by deleting files exceeding the quota
3. Try to recover the files from the trash bin
4. it's not possible to recover files if no enough space is left

Nextcloud Server version

30

Operating system

None

PHP engine version

PHP 8.1

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response