-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug]: Large file upload with an S3 backend always fails with 423 LOCKED #48823
Comments
This should be fixed with #27034 This requires |
I'll check this out, both to see if the server is ready for chunking v2 and the client sends what's needed. However unless chunking v1 is meant to disappear it would still be nice to have it fixed. Since there's no locking problem on files that manage to be properly uploaded, even the smaller big ones, I guess there's something messing up about locking that only happens when there's a NC to S3 error. Mayble a simple lock on a part that doesn't get released because of an uncaught exception. I'm going to try to setup an S3 test env and see if I can trigger systematically the behavior by mocking few things here and there. |
If you get a chance, it'd be helpful if you included your config ( Particularly since there are several elements at play (locking config, memcache config, object storage config, etc.) Re: the |
Follow-up: I was just reminded of this Issue: nextcloud/docker#1928 |
I'm getting similar error and cannot reliably upload files larger than 1GiB. example of an error:
Nextcloud config from my test instance.
|
Bug description
I'm trying to upload a 60GB file to a managed nextcloud instance running with an S3 backend. I'm using rclone as a client. The upload constantly fails for many reasons (judging by the stack traces in the logs) but the client-facing error is always
"REDACTED/REDACTED/REDACTED.REDACTED" is locked, existing lock on file: exclusive: OCA\DAV\Connector\Sabre\Exception\FileLocked: 423 Locked
.Steps to reproduce
Expected behavior
A successful upload with a 2XX status code or an actual 4XX/5XX error explaining what failed.
Nextcloud Server version
28
Operating system
None
PHP engine version
PHP 8.2
Web server
None
Database engine version
MySQL
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?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
Additional info
More context :
move
to assemble the file part. The upload toward NC is fine, it fails when pushing the parts from the virtually assembled stream to the S3 bucket (judging by the traces I've seen)sorry can't fix that
at this pointSome investigations :
chunkv2
scenario : the chunk are uploaded to some tmp directory and then moved to the S3 bucket as they are virtually assembledwriteMultiPart
of theS3ObjectTrait
MultipartUploader
that triggers the problem or if the timing also plays a role : the whole upload process takes up to an hour.The text was updated successfully, but these errors were encountered: