Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
[BR]
type = swift
user = TURNER
auth = https://authenticate.ain.net
auth_version = 2
tenant = storage
key = SUPERSECRET
endpoint_type = public
leave_parts_on_error = true
chunk_size = 1P
no_chunk = false
A log from the command that you were trying to run with the -vv flag
2023/10/24 10:23:28 DEBUG : rclone: Version "v1.64.2" starting with parameters ["C:\\Users\\Administrator\\Downloads\\rclone-v1.61.1-windows-amd64\\rclone.exe" "copy" "D:\\VMware-VCSA-all-8.0.1-22088981.iso" "BR:TURNER/T" "-P" "-vvv"]
2023/10/24 10:23:28 DEBUG : Creating backend with remote "D:\\VMware-VCSA-all-8.0.1-22088981.iso"
2023/10/24 10:23:28 DEBUG : Using config file from "C:\\Users\\Administrator\\AppData\\Roaming\\rclone\\rclone.conf"
2023/10/24 10:23:28 DEBUG : fs cache: adding new entry for parent of "D:\\VMware-VCSA-all-8.0.1-22088981.iso", "//?/D:/"
2023/10/24 10:23:28 DEBUG : Creating backend with remote "BR:TURNER/T"
2023/10/24 10:23:29 DEBUG : VMware-VCSA-all-8.0.1-22088981.iso: Need to transfer - File not found at Destination
2023/10/24 10:23:30 ERROR : VMware-VCSA-all-8.0.1-22088981.iso: Failed to copy: Too Large Object
2023/10/24 10:23:30 ERROR : Attempt 1/3 failed with 1 errors and: Too Large Object
2023/10/24 10:23:30 DEBUG : VMware-VCSA-all-8.0.1-22088981.iso: Need to transfer - File not found at Destination
2023/10/24 10:23:30 ERROR : VMware-VCSA-all-8.0.1-22088981.iso: Failed to copy: Too Large Object
2023/10/24 10:23:30 ERROR : Attempt 2/3 failed with 1 errors and: Too Large Object
2023/10/24 10:23:30 DEBUG : VMware-VCSA-all-8.0.1-22088981.iso: Need to transfer - File not found at Destination
2023/10/24 10:23:30 ERROR : VMware-VCSA-all-8.0.1-22088981.iso: Failed to copy: Too Large Object
2023/10/24 10:23:30 ERROR : Attempt 3/3 failed with 1 errors and: Too Large Object
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Errors: 1 (retrying may help)
Elapsed time: 2.1s
2023/10/24 10:23:30 INFO :
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Errors: 1 (retrying may help)
Elapsed time: 2.1s
2023/10/24 10:23:30 DEBUG : 5 go routines active
2023/10/24 10:23:30 Failed to copy: Too Large Object
My assumption is this has something to do with chunking/segmentation.
I've tried the below config, and still receiving "Operation Forbidden"
[BRTEST]
type = swift
user = TURNER
auth = https://authenticate.ain.net
auth_version = 2
tenant = storage
endpoint_type = public
key = SUPERSECRET
I see CyberDuck is making a .".file-segments" folder, which appears to be 1GB segments, for the large file. Seems to be part of Dynamic Large Objects in Swift?
I noticed that, I didn't entirely understand the entire page.
I just know over 5GB works on their website, and CyberDuck(By doing the segments), so I'm hopeful there's something that can be done with Rclone. $1/TB is just hard to beat at the moment. But if it's too much hassle, may not be worth it.
I should mention Chunker is an option, I know -- but then I cannot access the files via their WebGUI.
I think they are trying to give some options which seems a bit strange.
If there is no file size limit, not sure why I'd use the chunker remote.
If you end up using that 1st line they list, you can only transfer a file no larger than 5GB. If you make it smaller, rclone 'chunks' the upload and uploads which is not related to chunker remote. Just sounds the same.
The problem is that on swift, rclone creates the chunks in a different container.
So if you are uploading into container any chunks will be put into container_segments. This is the recommended way of uploading chunks so they don't show in the directory listings and confuse things.
Blomp allows you access to one container only, so when rclone attempts to create container_segments it gets permission denied.
This currently isn't configurable but it could be with a bit more work. Rclone could make a .file-segments folder like CyberDuck does and store the chunks in there.
I finally received an updated response from Blomp.
"rclone tries to use dynamic large objects which requires permission to build additional containers for each upload. We don't allow that because we can't enforce quotas this way.
Static Large Objects we support, and would be glad to help write the code to commit to rclone to use this mode with Blomp"
So I'm not sure if that means they're working with you guys already on a fix?
