Bug 2019909
Summary: | [rbd-mirror] mirror image status - syncing_percent locked at 4 for an image of 50G+ during the sync | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vasishta <vashastr> |
Component: | RBD-Mirror | Assignee: | Ilya Dryomov <idryomov> |
Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.1 | CC: | akraj, ceph-eng-bugs, idryomov, tserlin, vereddy |
Target Milestone: | --- | ||
Target Release: | 5.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-16.2.8-65.el8cp | Doc Type: | Bug Fix |
Doc Text: |
.`last_copied_object_number` value is properly updated for all images
Previously, due to an implementation defect, `last_copied_object_number` value was properly updated only for fully allocated images. This caused the `last_copied_object_number` value to be incorrect for any sparse image and the image replication progress to be lost in case of abrupt rbd-mirror daemon restart.
With this fix, `last_copied_object_number` value is properly updated for all images and upon rbd-mirror daemon restart, image replication resumes from where it had previously stopped.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-09 17:36:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2102272 |
Description
Vasishta
2021-11-03 15:41:54 UTC
Working as expected with latest build. Hence moving to verified state. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Ceph Storage Security, Bug Fix, and Enhancement Update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5997 |