Open dautrich opened 1 year ago
Expected behavior
After reaching the quota limit, the synch process should be stopped immediately. Temporary directories/files in the user's 'uploads' directory should be deleted.
They are, but not just after upload fails; they are handled by a background job (every hour ifI remember correctly).
@solracsf In my webspace, there obviously was no background job to handle the situation. The directories/files in the user's 'uploads' directory were still there, taking all my available webspace. Who would be responsible for such a type of (cron) job: The installed Nextcloud instance? The webspace provider?
Nextcloud cronjob.
⚠️ This issue respects the following points: ⚠️
Bug description
This is a follow-up of (closed) bug report #29199, as requested there. I run a Nextcloud 25.0.5 in a shared web hosting space. Disk space in the hosting package is limited to 80 GB. There are only two Nextcloud users, plus admin. One of the users had a quota limit of 1 GB, but tried to upload a directory of about 1.8 GB, using the sync mechanism of the Windows client. After the quota limit was reached, something went topsy-turvy. The webspace was completely filled up. Login to the Nextcloud didn't work anymore. Examining with Filezilla, I found that the directory 'uploads' in the user's file space contained several thousands of subdirectories with randomly built filenames. Deleting the content of directory 'uploads' solved the issue for the moment. Then I increased the user's quota limit to 5 GB. After that, the remaining rest of the files seems to have been synched to the Nextcloud without user intervention. But thereafter, the uploads directory again contained several hundreds of subdirectories, which I had to manually delete again.
Steps to reproduce
Expected behavior
After reaching the quota limit, the synch process should be stopped immediately. Temporary directories/files in the user's 'uploads' directory should be deleted.
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
25
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 22.2.3 to 22.2.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response