[Bug]: “Your storage is full, files can not be updated or synced anymore!” notification is displayed to users with quota set to 0 Bytes

[jkhradil]

⚠️ 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

Nextcloud shows “Your storage is full, files can not be updated or synced anymore!” notification when user's quota is exceeded or backend storage is full. Since version 28 this notification is also displayed to users with quota set to 0 Bytes. This quota is commonly used to create "read-only" users, to whom this notification is confusing and it would be better if wasn't shown.

Steps to reproduce

1. Cerate a user with quota set to 0 Bytes.
2. Login as this user.
3. See “Your storage is full, files can not be updated or synced anymore!” notification.

Expected behavior

“Your storage is full, files can not be updated or synced anymore!” should not be displayed to users with quota set to 0 Bytes.

Installation method

None

Nextcloud Server version

28

Operating system

None

PHP engine version

None

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

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

I can send PR with a fix if you'll agree.

[solracsf]

I can send PR with a fix if you'll agree.

Please do :)

[jsobiecki]

I confirm this issue with latest nextcloud (28.0.2).

[veitw]

Same issue for me. My users are only allowed to store files inside group folders and hence have a personal quota of 0 bytes. They are quite confused being permanently confronted with this notification.

Seconding integration of jkhradil's patch.