#10465 closed defect (duplicate)
Uploading to B2 Backblaze. Failed uploads.
Reported by: | Super68 | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.8.3 |
Component: | b2 | Version: | 6.7.1 |
Severity: | normal | Keywords: | |
Cc: | Architecture: | ||
Platform: |
Description (last modified by dkocher)
Hi. I'm a newbie to both CyberDuck and B2 although I've used Backblaze for a number of year. Technically I learn fast but I'm just finding my feet. I'm using [paid up member!] CyberDuck to upload my archive files to B2. Im in film so MANY of the files are big .mov files, over a gig. I'm running a test and some have failed. So, a few questions;
Am I doing something wrong?!? Can I get a list of files that didn't upload? Can you automate uploads?
Happy to provide any info you need! Best, Brian
HTTP/1.1 200 Cache-Control: max-age=0, no-cache, no-store Content-Type: application/json;charset=utf-8 Content-Length: 248 Date: Mon, 17 Sep 2018 14:22:23 GMT POST /b2api/v1/b2_list_buckets HTTP/1.1 Authorization: ******** Content-Length: 28 Content-Type: application/json; charset=UTF-8 Host: api001.backblazeb2.com Connection: Keep-Alive User-Agent: Cyberduck/6.7.1.28683 (Mac OS X/10.13.6) (x86_64) Accept-Encoding: gzip,deflate HTTP/1.1 200 Cache-Control: max-age=0, no-cache, no-store Content-Type: application/json;charset=utf-8 Content-Length: 543 Date: Mon, 17 Sep 2018 14:22:25 GMT POST /b2api/v1/b2_list_file_versions HTTP/1.1 Authorization: ******** Content-Length: 134 Content-Type: application/json; charset=UTF-8 Host: api001.backblazeb2.com Connection: Keep-Alive User-Agent: Cyberduck/6.7.1.28683 (Mac OS X/10.13.6) (x86_64) Accept-Encoding: gzip,deflate HTTP/1.1 200 Cache-Control: max-age=0, no-cache, no-store Content-Type: application/json;charset=utf-8 Content-Length: 1477 Date: Mon, 17 Sep 2018 14:22:25 GMT POST /b2api/v1/b2_get_upload_part_url HTTP/1.1 Authorization: ******** Content-Length: 96 Content-Type: application/json; charset=UTF-8 Host: api001.backblazeb2.com Connection: Keep-Alive User-Agent: Cyberduck/6.7.1.28683 (Mac OS X/10.13.6) (x86_64) Accept-Encoding: gzip,deflate HTTP/1.1 200 Cache-Control: max-age=0, no-cache, no-store Content-Type: application/json;charset=utf-8 Content-Length: 376 Date: Mon, 17 Sep 2018 14:22:25 GMT POST /b2api/v1/b2_upload_part/4_zadc747cd1a5cda8563540419_f203ae0c693a79fb3_d20180917_m140451_c001_v0001106_t0024/0014 HTTP/1.1 Authorization: ******** X-Bz-Part-Number: 8 X-Bz-Content-Sha1: 9db05f770387dc3dba6aed8a9860396b143a740e Content-Length: 104857600 Content-Type: application/octet-stream Host: pod-000-1106-12.backblaze.com Connection: Keep-Alive User-Agent: Cyberduck/6.7.1.28683 (Mac OS X/10.13.6) (x86_64) Accept-Encoding: gzip,deflate
Attachments (1)
Change History (6)
Changed on Sep 17, 2018 at 2:24:06 PM by Super68
comment:1 Changed on Oct 4, 2018 at 9:21:13 AM by dkocher
- Description modified (diff)
comment:2 Changed on Oct 4, 2018 at 9:22:26 AM by dkocher
comment:3 Changed on Oct 4, 2018 at 9:22:36 AM by dkocher
- Component changed from core to b2
- Priority changed from high to normal
comment:4 Changed on Oct 7, 2018 at 12:43:40 PM by Iritscen
I believe I am experiencing the same issue with v6.8.0. I occasionally want to upload files of around 20-25GB each to a B2 bucket. The behavior I witnessed in 6.8.0 is pretty odd: there is constant heavy disk activity, even after the checksum is calculated and the upload is proceeding, as well as massive CPU usage. Additionally, the transfer I attempted failed after a few gigabytes and was unable to resume despite thrashing the CPU and disk for a long time. I reverted to Cyberduck 6.6.2 and it allows me to upload these files just fine, with minimal CPU and disk usage.
comment:5 Changed on Oct 31, 2018 at 4:31:21 PM by dkocher
- Milestone set to 6.8.3
- Resolution set to duplicate
- Status changed from new to closed
Duplicate for #10516.
Can you share the error message that is displayed for failed uploads.