Actions
Bug #11334
closedosd: op with newer epoch stuck in optracker
Status:
Can't reproduce
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
log shows
2015-04-04 20:21:19.807227 7f628f9e9700 1 -- 10.214.136.136:6800/24788 <== mds.0 10.214.134.10:6800/9790 125281 ==== osd_op(mds.0.122:43197967 1000a878d0c.00000000 [create 0~0,setxattr parent (342)] 0.47732881 ondisk+write+known_if_redirected e406836) v5 ==== 217+0+348 (1980847806 0 3494425867) 0x201c9500 con 0x1e92ac60
2015-04-04 20:21:19.807306 7f628f9e9700 1 -- 10.214.136.136:6800/24788 --> 10.214.133.104:6789/0 -- mon_subscribe({monmap=6+,osd_pg_creates=0,osdmap=406836}) v2 -- ?+0 0x38d7400 con 0x1f163c60
and then starts complaining about a blocked op.
Actions