Actions
Bug #17173
closedDuplicate damage table entries
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Seen on mira021 long-running MDS.
(where j is the damage json) >>> [d for d in j if d['ino'] == 1099529116670] [{u'frag': u'*', u'ino': 1099529116670, u'damage_type': u'dir_frag', u'id': 197657288}, {u'frag': u'*', u'ino': 1099529116670, u'damage_type': u'dir_frag', u'id': 244045365}]
The inserting logic should be checking for existing entry of same inode+type before inserting, but apparently it's not. There are only 670 unique inodes mentioned, but there are 1352 entries in the damage table.
Updated by John Spray over 7 years ago
- Status changed from New to Fix Under Review
Updated by John Spray over 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Loïc Dachary over 7 years ago
- Copied to Backport #17479: jewel: Duplicate damage table entries added
Updated by Loïc Dachary over 7 years ago
- Status changed from Pending Backport to Resolved
Actions