On Thu, Oct 31, 2013 at 6:22 AM, Dominik Mostowiec <dominikmostowiec@xxxxxxxxx> wrote: > Hi, > I have strange radosgw error: > > ====== > 2013-10-26 21:18:29.844676 7f637beaf700 0 setting object > tag=_ZPeVs7d6W8GjU8qKr4dsilbGeo6NOgw > 2013-10-26 21:18:30.049588 7f637beaf700 0 WARNING: set_req_state_err > err_no=125 resorting to 500 > 2013-10-26 21:18:30.049738 7f637beaf700 2 req 61655:0.224186:s3:POST > /testbucket/files/image%20%286%29.jpeg:complete_multipart:http > status=500 > 2013-10-26 21:18:30.049975 7f637beaf700 1 ====== req done > req=0x11013d0 http_status=500 ====== > > It's similar to: http://tracker.ceph.com/issues/5439 > This is the same bug? > My ceph version: > ceph version 0.56.6 (95a0bda7f007a33b0dc7adf4b330778fa1e5d70c) > > Bug (5439) is fixed. > How to check (if I know commit > "72d4351ea5a470051e428ffc5531acfc7d1c7b6f" ) which CEPH version have > this fix. > In latest bobtail - 0.56.7 it is fixed? That particular commit is in dumpling and all subsequent dev releases. (I checked by using "git tag --contains" in my git checkout.) It's not in Bobtail, but I'm not sure when the behavior changed to become incorrect (or whether Bobtail is susceptible to that particular bug). I'd upgrade if I were you and test it out — behavior in a variety of component failure conditions is much better under later versions than it is under Bobtail! -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |