Actions
Bug #2863
closedclient: does not tolerate traceless replies from mds
Status:
Resolved
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
In at least one case (_create's _mknod) we do not tolerate a (write) reply from the mds with no trace. This happens when there are socket failures and needs to be tolerate.
The first step is to instrument the client code to artificially trigger this on every update request. Then we can ensure we correctly handle it in all cases by running a full suite with that option.
Updated by Sage Weil over 11 years ago
- Project changed from Ceph to CephFS
- Category deleted (
26)
Updated by Greg Farnum about 10 years ago
- Priority changed from Normal to Low
uclient failure-case: low priority.
I believe we've established that the kclient does not suffer from this issue, correct?
Actions