[Bug]: File deleted when moved into an overfilled S3 bucket
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ 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
When a document is moved to an S3 bucket which is at its quota, the file simply disappears into the void with no error message displayed to the user. There is an error displayed in the log file, however. This issue does not affect larger files, e.g. 128 MB. Maybe it has to do with the chunking mechanism for larger files or something.
Steps to reproduce
- Have an S3 bucket which is already filled to its quota.
- Move a small document there (a few kilobytes in size maybe)
- It should disappear without an error
Expected behavior
The document / file should remain present, and an error message should be shown to the user just as it is with larger files.
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
No response
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
Start by reproducing the move with a small document in an S3 bucket at quota, then compare it with the reported 128 MB case and inspect the server log error. Done means the small file remains present and the user sees an error, matching the behavior expected for larger files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100