Bug #7937
[ERR] deep-scrub 5.ds0 79d5820d/burnupi0838757-23/1f7//5 expected clone
0%
Description
2014-03-31 17:00:27,792.792 INFO:teuthology.task.internal:Removing archive directory...
2014-03-31 17:00:27,840.840 INFO:teuthology.task.internal:Tidying up after the test...
2014-03-31 17:00:27,976.976 INFO:teuthology.run:Summary data:
{duration: 2701.271768093109, failure_reason: '"2014-03-31 16:53:21.038262 osd.2 10.214.134.34:6810/58421
216 : [ERR] deep-scrub 5.ds0 79d5820d/burnupi0838757-23/1f7//5 expected clone
0//1f7//-1" in cluster log', flavor: basic, owner: samuelj@slider, success: false}
Associated revisions
osd/ReplicatedPG: handle snapdir properly during scrub
Handle snapdir similarly to how head is treated when updating the
next_clone info. Also, add a warning when we have a snapdir object and
head_exists == true (the converse of the existing check).
Fixes: #7937
Signed-off-by: Sage Weil <sage@inktank.com>
ReplicatedPG::_scrub: don't bail early for snapdir
Fixes: #7937
Signed-off-by: Samuel Just <sam.just@inktank.com>
History
#1 Updated by Samuel Just almost 10 years ago
038e94b51e4945380c4ba771c88c953b6628d0f7 (wip-sam-testing)
#2 Updated by Sage Weil almost 10 years ago
- Subject changed from 216 : [ERR] deep-scrub 5.ds0 79d5820d/burnupi0838757-23/1f7//5 expected clone to [ERR] deep-scrub 5.ds0 79d5820d/burnupi0838757-23/1f7//5 expected clone
- Category set to OSD
- Status changed from New to Fix Under Review
#3 Updated by Sage Weil almost 10 years ago
- Status changed from Fix Under Review to 7
#4 Updated by Sage Weil almost 10 years ago
- Assignee set to Samuel Just
#5 Updated by Samuel Just almost 10 years ago
- Status changed from 7 to Resolved