Actions
Bug #53826
closedrbd-mirror: captures debug log in rbd mirror status last update
Status:
Closed
Priority:
Low
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2022-01-11T08:26:07.413+0000 7f8f88f25700 10 librbd::mirror::GetInfoRequest: 0x560af48fbbd0 calc_promotion_state: promotion_state=1, primary_mirror_uuid=a1: global_id: 612080f8-b205-4679-bca4-8ab2644b672f state: up+stopped description: local image is primary service: admin on vossi03 last_update: 2022-01-11T08:26:07.413+0000 7f8f88f25700 20 librbd::mirror::GetInfoRequest: 0x560af48fbbd0 finish: r=02022-01-11 08:25:44 peer_sites: name: primary state: up+replaying description: replaying, {"bytes_per_second":0.0,"bytes_per_snapshot":0.0,"remote_snapshot_timestamp":1641889534,"replay_state":"idle"} last_update: 2022-01-11 08:25:44 snapshots:
last_update: 2022-01-11T08:26:07.413+0000 7f8f88f25700 20 librbd::mirror::GetInfoRequest: 0x560af48fbbd0 finish: r=02022-01-11 08:25:44
should be just last_update: 2022-01-11 08:25:44
Similar, other instance
state: up+replaying2022-01-11T08:40:44.841+0000 7f02592af380 20 librbd::api::Snapshot: list: snap_list 0x557449d925c0
Snap listing also has this issue
SNAPID 2022-01-11T15:45:39.722+0000 7f3729ffb700 5 librbd::io::Dispatcher: 0x55fea5765fc0 register_dispatch: dispatch_layer=1NAME SIZE PROTECTED TIMESTAMP 2022-01-11T15:45:39.722+0000 7f3729ffb700 10 librbd::ImageState: 0x55fea5765f40 0x55fea5765f40 handle_open: r=0 NAMESPACE 183 .mirror.primary.ce3375e2-b6e8-41c3-b959-d3ae6f517bb0.af63dda5-994c-418f-a1b2-13197fa5cf03 1 GiB 2022-01-11T15:45:39.722+0000 7f3738329380 20 librbd::api::Snapshot: list: snap_list 0x55fea571e840Tue Jan 11 15:41:12 2022 mirror (demoted peer_uuids:[4ab979b6-f1b9-437f-a3a1-a99afa321acf])
Updated by Ilya Dryomov over 2 years ago
Are you saying that normal output can get mixed with debug output when you append e.g. --debug-rbd to your commands? If so, I think that is expected. It is just an artifact of pushing two unsynchronized output streams to the same destination.
Updated by Deepika Upadhyay over 2 years ago
- Status changed from New to Closed
Thanks for the clarification Ilya, looks harmless in this case; closing until we find otherwise.
Actions