-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Federation: Upload reports insufficient storage but we are far from any limit #29169
Comments
Not sure yet but could be related to #29103 which I haven't been able to reproduce yet |
note: it's a chunked upload on new DAV endpoint (see the |
Added an automated test to upload to a received federated share when quota is applied, the test passes: #29193 Need further research, I think the scenario here is a bit different anyway |
The incident first occurred was on Friday night with many activities for client syncing. One idea is, and maybe I am wrong, that oC gets confused when a file that is currently beeing in process of federation sync gets a new version via the client autosync. And somehow there is a internal job running regularly that cleans up whatever was messed up. Just my 2c |
Hmmm not sure... now that you talk about stuff "being in process" this reminds me of part files. Can you check if the folder in question contains any stray ".part" files ? I suppose this could skew quota calculation as these files are not indexes, so their size does not count. But my gut feeling says the problem is somewhere else. |
The problem is reproducible, but only with the desktop client upload:
Expected: sync goes through I suspect that the difference is that the desktop client might set more headers in the final MOVE, one related to the final size or something, and somehow this seems to make the quota check bug. I'll debug this... |
oh come on... I thought this was fixed before: QuotaPlugin does call |
Ok now I also see the error in the web UI... weird... Nevertheless, here is the task list:
|
Fix is here: #29220 |
Thanks for the fix |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
Expected behaviour
No errors
Actual behaviour
Error reported about insufficient storage via oC client or browser
Upload to the local 10.0.3 instance or 10.0.2 instance works (no federation)
Upload to the federation target (10.0.2) directly, works and is distributed afterwards to 10.0.3 and W10
Free space local: 37GB
Free space remote: >200GB
No change if set in config.php
quota_include_external_storage = false
No local/remote user quota limit reached
Creating 2 nested directories with some smaller files in but in total 33MB (which is of course higher than the single 24MB file) than the upload via 10.0.3 to the federation works = single filesize matters.
It worked before in this combination and suddenly stopped. The federation accepted filesizes of 350MB+ without any problems.
Server configuration
Operating system: Ubuntu 16.04
Web server: nginx
Database: mysql
PHP version: 7.0
ownCloud version: 10.0.3
Updated from an older ownCloud or fresh install: updated
Where did you install ownCloud from: tar
Signing status (ownCloud 9.0 and above): no problems
The content of config/config.php:
config_report_20171008.txt
List of activated apps:
Are you using external storage, if yes which one: smb, federation
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Opera
Operating system: W10x64
ownCloud log (data/owncloud.log)
The text was updated successfully, but these errors were encountered: