Re: [ceph-users] radosgw multipart-uploaded downloads fail

2014-04-08 Thread mykr0t
Hi, It was a 256 gig file ERROR: S3 error: 416 (InvalidRange): I think this is a MaxParts default limit 1000, s3cmd default part size 15MB (see .s3cfg). I cant find right way how to change this limit on rgw side, so i change part size in .s3cfg or use multipart tar archive for large files. --

Re: [ceph-users] radosgw multipart-uploaded downloads fail

2014-04-04 Thread Benedikt Fraunhofer
2014-04-04 0:31 GMT+02:00 Yehuda Sadeh yeh...@inktank.com: Hi Yehuda, sorry for the delay. We ran into another problem and this took up all the time. Are you running the version off the master branch, or did you just cherry-pick the patch? I can't seem to reproduce the problem. I just patched

Re: [ceph-users] radosgw multipart-uploaded downloads fail

2014-04-03 Thread Yehuda Sadeh
Ok, we were able to reproduce it. Opened issue #7978, and there's a fix pending for upstream. Thanks, Yehuda On Wed, Apr 2, 2014 at 7:20 AM, Yehuda Sadeh yeh...@inktank.com wrote: On Wed, Apr 2, 2014 at 2:08 AM, Benedikt Fraunhofer given.to.lists.ceph-users.ceph.com.toasta@traced.net

Re: [ceph-users] radosgw multipart-uploaded downloads fail

2014-04-02 Thread Benedikt Fraunhofer
Hi Yehuda, i tried your patch and it feels fine, except you might need some special handling for those already corrupt uploads, as trying to delete them gets radosgw in an endless loop and high cpu usage: 2014-04-02 11:03:15.045627 7fbf157d2700 0 RGWObjManifest::operator++(): result:

[ceph-users] radosgw multipart-uploaded downloads fail

2014-04-01 Thread Benedikt Fraunhofer
Hello everyone, I can't download anything that's been uploaded as a multipart-upload. I'm on 0.78 (f6c746c314d7b87b8419b6e584c94bfe4511dbd4) on a non-ec-pool. The upload is acknowledged as beeing ok 2014-03-31 14:56:56.722727 7f4080ff9700 2 req 8:0.023285:s3:POST

Re: [ceph-users] radosgw multipart-uploaded downloads fail

2014-04-01 Thread Benedikt Fraunhofer
Hi Yehuda, 2014-04-01 15:49 GMT+02:00 Yehuda Sadeh yeh...@inktank.com: It could be the gateway's fault, might be related to the new manifest that went in before 0.78. I'll need more logs though, can you reproduce with 'debug ms = 1', and 'debug rgw = 20', and provide a log for all the