Bug #50523
closed
Mirroring path "remove" don't not seem to work
Added by Sébastien Han about 3 years ago.
Updated almost 3 years ago.
Description
Consider the following:
runner@fv-az120-169:~/work/rook/rook$ kubectl exec -n rook-ceph-secondary deploy/rook-ceph-tools -t -- ceph fs snapshot mirror add myfs /v
{}
runner@fv-az120-169:~/work/rook/rook$ kubectl exec -n rook-ceph-secondary deploy/rook-ceph-tools -t -- ceph fs snapshot mirror add myfs /
Error EINVAL: / is a ancestor of tracked path /v
command terminated with exit code 22
runner@fv-az120-169:~/work/rook/rook$ kubectl exec -n rook-ceph-secondary deploy/rook-ceph-tools -t -- ceph fs snapshot mirror remove myfs /v
{}
runner@fv-az120-169:~/work/rook/rook$ kubectl exec -n rook-ceph-secondary deploy/rook-ceph-tools -t -- ceph fs snapshot mirror add myfs /
Error EINVAL: / is a ancestor of tracked path /v
command terminated with exit code 22
Waiting a few minutes does not change anything.
- Status changed from New to Triaged
- Assignee set to Venky Shankar
- Target version set to v17.0.0
- Backport set to pacific
- Status changed from Triaged to In Progress
I can reproduce this when mirror daemon is not running (guessing that your case too):
$ ceph fs snapshot mirror remove cephfs /d0/d1
{}
$ ceph fs snapshot mirror remove cephfs /d0/d1
Error EINVAL: directory /d0/d1 is under removal
The omap entry for this directory still exists:
cephalopod@cephalopod-octo:/work/ceph/build$ rados -p cephfs.meta listomapvals cephfs_mirror
dir_map_/d0/d1
value (80 bytes) :
00000000 80 03 7d 71 00 28 58 07 00 00 00 76 65 72 73 69 |..}q.(X....versi|
00000010 6f 6e 71 01 4b 01 58 0b 00 00 00 69 6e 73 74 61 |onq.K.X....insta|
00000020 6e 63 65 5f 69 64 71 02 4e 58 0d 00 00 00 6c 61 |nce_idq.NX....la|
00000030 73 74 5f 73 68 75 66 66 6c 65 64 71 03 4e 58 07 |st_shuffledq.NX.|
00000040 00 00 00 70 75 72 67 69 6e 67 71 04 4b 01 75 2e |...purgingq.K.u.|
00000050
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 41084
- Status changed from Fix Under Review to Pending Backport
- Source set to Community (dev)
- Copied to Backport #50917: pacific: Mirroring path "remove" don't not seem to work 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