Bug #40784
closed
mds: metadata changes may be lost when MDS is restarted
Added by shen hang almost 5 years ago.
Updated about 4 years ago.
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:
root@xxx.yyy:/zzz/src1
- cp src969 src123
root@xxx.yyy:/zzz/src1
- ls
^C^C^C^C^C^C^C^C
root@xxx.yyy:/zzz/src1
- ls
src969
- 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
- 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 )
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #43344: mimic: mds: metadata changes may be lost when MDS is restarted added
- Copied to Backport #43345: nautilus: mds: metadata changes may be lost when MDS is restarted added
- 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".
Also available in: Atom
PDF