On Fri, Dec 14, 2018 at 4:27 PM Vikas Rana <[email protected]> wrote: > > Hi there, > > We are replicating a RBD image from Primary to DR site using RBD mirroring. > We were using 10.2.10. > > We decided to upgrade the DR site to luminous and upgrade went fine and > mirroring status also was good. > We then promoted the DR copy to test the failure. Everything checked out good. > > The issue now is, we are not able to resume our replication. Its complaining > about "description: remote image does not exist" > This was the same image which were in mirroring relationship before the > promotion. > We compared the mirroring global id and they are not matching. When we did > the testing in lab, this value is same on both side. > > > > rbd info nfs/dir_research > > rbd image 'dir_research': > > size 200 TB in 52428800 objects > > order 22 (4096 kB objects) > > block_name_prefix: rbd_data.edd65238e1f29 > > format: 2 > > features: layering, exclusive-lock, journaling > > flags: > > journal: edd65238e1f29 > > mirroring state: enabled > > mirroring global id: a8522ed7-70ff-4966-9edc-e7ef41906fd9 > > mirroring primary: true > > > rbd --cluster cephdr info nfs/dir_research > > rbd image 'dir_research': > > size 200TiB in 52428800 objects > > order 22 (4MiB objects) > > block_name_prefix: rbd_data.58e76109cf92e > > format: 2 > > features: layering, exclusive-lock, journaling > > flags: > > journal: 58e76109cf92e > > mirroring state: enabled > > mirroring global id: 1490c637-21f9-4eff-bef6-54defc1e0988 > > mirroring primary: false > > > > rbd mirror image status nfs/dir_research > > dir_research: > > global_id: a8522ed7-70ff-4966-9edc-e7ef41906fd9 > > state: down+unknown > > description: status not found > > last_update: 1969-12-31 19:00:00
It's odd that this image is not reporting any status. Do you have an "rbd-mirror" daemon still running against this cluster? > > rbd --cluster cephdr mirror image status nfs/dir_research > > dir_research: > > global_id: 1490c637-21f9-4eff-bef6-54defc1e0988 > > state: down+error > > description: remote image does not exist > > last_update: 2018-11-30 11:28:49 > > > > > > > So the question is, Is it possible the mirroring global id got changed after > upgrade and is there's any way to change the global id to match the > production so that the replication can be resumed. Can you provide the output from the following commands (run against both clusters)? rados -p nfs getomapval rbd_mirroring mirror_uuid rbd mirror pool info --pool nfs rbd journal status --pool nfs --image dir_research > > > Thanks, > > -Vikas > > > _______________________________________________ > ceph-users mailing list > [email protected] > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- Jason _______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
