Bug #27657
mds: retry remounting in ceph-fuse on dcache invalidation
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
luminous,mimic
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
ceph-fuse
Labels (FS):
crash
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Right now, failure in remounting on dcache invalidation results in the following crash:
1: (()+0x6d1ff4) [0x55f21052fff4]
2: (()+0x11390) [0x7f7f92e11390]
3: (gsignal()+0x38) [0x7f7f91b9d428]
4: (abort()+0x16a) [0x7f7f91b9f02a]
5: (Client::_do_remount()+0x303) [0x55f2100ee8a3]
6: (Context::complete(int)+0x9) [0x55f2100f0bb9]
7: (Finisher::finisher_thread_entry()+0x460) [0x55f21015bbd0]
8: (()+0x76ba) [0x7f7f92e076ba]
9: (clone()+0x6d) [0x7f7f91c6f41d]
This was seen in luminous but exists in master too. errno returned is 12, but mount(3) return codes are ORed (Thanks Patrick).
For the fix -- its best to not abort and retry the remount operation. Also, fix how errno is interpreted in this case.
Related issues
History
#1 Updated by Venky Shankar over 5 years ago
- Status changed from New to In Progress
#2 Updated by Venky Shankar over 5 years ago
- Backport set to luminous,mimic
#3 Updated by Venky Shankar over 5 years ago
- Status changed from In Progress to Fix Under Review
#4 Updated by Patrick Donnelly over 5 years ago
- Status changed from Fix Under Review to Pending Backport
#5 Updated by Nathan Cutler over 5 years ago
- Copied to Backport #35931: luminous: mds: retry remounting in ceph-fuse on dcache invalidation added
#6 Updated by Nathan Cutler over 5 years ago
- Copied to Backport #35932: mimic: mds: retry remounting in ceph-fuse on dcache invalidation added
#7 Updated by Patrick Donnelly about 5 years ago
- Status changed from Pending Backport to Resolved