Actions
Bug #40784
closedmds: metadata changes may be lost when MDS is restarted
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Assumed a client copied some obj to another location in ceph. when early_replied was received , the cp command would return normally。But the op may not be journaled when the mds was restarted. If the client didn't send reconnect msg duiring reconnect phase in time,t he obj may not exists in the destination location.
It looks like below:
- cp src969 src123
root@xxx.yyy:/zzz/src1 - ls
^C^C^C^C^C^C^C^C
root@xxx.yyy:/zzz/src1 - ls
src969
Updated by Patrick Donnelly over 4 years ago
- Project changed from Ceph to CephFS
- Subject changed from data may be lost when mds is restarted,and client didn't send reconnect msg during reconnect phase to mds: data may be lost when mds is restarted,and client didn't send reconnect msg during reconnect phase
- Status changed from New to Fix Under Review
- Assignee set to shen hang
- Start date deleted (
07/16/2019) - Backport changed from nautilus,mimic,luminous to nautilus,mimic
- Component(FS) MDS added
Updated by Patrick Donnelly over 4 years ago
- Subject changed from mds: data may be lost when mds is restarted,and client didn't send reconnect msg during reconnect phase to mds: metadata changes may be lost when MDS is restarted
- Tags deleted (
cephfs mds)
Updated by Patrick Donnelly over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43344: mimic: mds: metadata changes may be lost when MDS is restarted added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43345: nautilus: mds: metadata changes may be lost when MDS is restarted added
Updated by Nathan Cutler about 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions