Bug #1536: rgw fails many s3tests due to bad clone_range usage - rgw - Ceph

Actions

Copy link

Bug #1536

closed

rgw fails many s3tests due to bad clone_range usage

Added by Josh Durgin over 12 years ago. Updated over 6 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

On commit:9b6f3e1679ffa146e6d1d8995d3901410de87606 this is in the logs many times:

2011-09-12 12:26:44.974160 7f20117fa700 can't clone object test-client.0-9glhz5ibbqhq40d-5:foo to shadow object, tag/shadow_obj haven't been set
2011-09-12 12:26:44.974226 7f20117fa700 calling op.clone_range(dst_ofs=0, src.object=_tmp_foo_X7UvQiF_ynohG1G4XP-wtyDszLNd8EV range.src_ofs=0 range.len=3
2011-09-12 12:26:45.058376 7f20117fa700 --> Status: 404

$ zgrep -c "can't clone" ~teuthworker/archive/nightly_coverage_2011-09-12/153/remote/ubuntu@sepia47.ceph.dreamhost.com/log/rgw.log.gz
95

Actions

Copy link

Updated by Yehuda Sadeh over 12 years ago

That warning is harmless, the object did not exist, so we couldn't clone it. This looks like the culprit:

2011-09-14 00:41:09.056231 7f6f9f7fe710 -- 10.0.1.245:0/1012217 --> 10.0.1.203:6800/20263 -- osd_op(client4116.0:31 bar [delete,create 0~0,setxattr user.rgw.acl (81),setxattr user.rgw.content_type (25),setxattr user.rgw.etag (33),setxattr user.rgw.idtag (32),setxattr user.rgw.shadow_name (36),clonerange 0~3 from _tmp_bar_7DQ51HUn_Wg6R2_EUBJXtDCj05t1LVU/head offset 0] 468.efe6384b) v1 -- ?+0 0x1141a80 con 0x1107dd0
2011-09-14 00:41:09.057417 7f6fa65a9710 -- 10.0.1.245:0/1012217 <== osd0 10.0.1.203:6800/20263 35 ==== osd_op_reply(31 bar [delete,create 0~0,setxattr (81),setxattr (25),setxattr (33),setxattr (32),setxattr (36),clonerange 0~3 from /0 offset 0] ack = -2 (No such file or directory)) v2 ==== 360+0+0 (2138230504 0 0) 0x1146010 con 0x1107dd0

Yet to verify that, but it looks like it ignores the FAILOK flag in the delete op.

Actions

Copy link