Can you share 'ceph versions' output?
Do you see the same behaviour when adding a snapshot schedule, e.g.
rbd -p mirror snapshot schedule add 30m
I can't reproduce it, unfortunately, creating those mirror snapshots
manually still works for me.
Zitat von scott.cai...@tecnica-ltd.co.uk:
We h
We have rbd-mirror daemon running on both sites, however replication is only
one way (i.e. the one on the remote site is the only live one, the one on the
primary site is just there for if we ever need to set up two-way, but this is
not currently set up for any replication - so it makes sense th
Hi,
I think I need some clarification. You have a rbd-mirror daemon
running on the primary site although you have configured rbd-mirroring
one-way only? And those errors you see in the rbd-mirror daemon log on
the primary site?
Maybe the daemon got started/activated by accident (or it was n
Thanks - side tracked with other work so only just got around to testing this.
Unfortunately when enabling rbd-mirror logs on the source cluster I'm not
seeing any events logged at all, however on the remote cluster I can see
constant activity (mostly imageReplayer, mirrorStatusUpdater, etc. log
Hi,
sorry for the delayed response, I was on vacation.
I would set the "debug_rbd_mirror" config to 15 (or higher) and then
watch the logs:
# ceph config set client.rbd-mirror. debug_rbd_mirror 15
Maybe that reveals anything.
Regards,
Eugen
Zitat von scott.cai...@tecnica-ltd.co.uk:
Thank
Thanks - hopefully I'll hear back from devs then as I can't seem to find
anything online about others encountering the same warning, but I surely can't
be the only one!
Would it be the rbd subsystem I'm looking to increase to debug level 15 or is
there another subsystem for rbd mirroring?
What
Hi,
I don't have much to contribute, but according to the source code [1]
this seems to be a non-fatal message:
void CreatePrimaryRequest::handle_unlink_peer(int r) {
CephContext *cct = m_image_ctx->cct;
ldout(cct, 15) << "r=" << r << dendl;
if (r < 0) {
lderr(cct) << "failed to un
