Bug 2366626
| Summary: | [8.0z backport]rgw: tail objects are wrongly deleted in copy_object | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Bipin Kunal <bkunal> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | Chaithra <ckulal> |
| Severity: | urgent | Docs Contact: | Rivka Pollack <rpollack> |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | ceph-eng-bugs, cephqe-warriors, ivancich, mbenjamin, mcaldeir, mkasturi, rpollack, tpetr, tserlin |
| Target Milestone: | --- | Flags: | mkasturi:
needinfo+
|
| Target Release: | 8.0z4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-19.2.0-132.el9cp | Doc Type: | Bug Fix |
| Doc Text: |
.Tail objects no longer wrongly deleted with `copy-object`
Previously, there was a reference count invariant on tail objects that was not maintained when an object was copied to itself. This caused the existing object was changed, rather than copied. As a result, references to tail objects were being decremented. When the refcount on tail objects dropped to 0, they were deleted during the next garbage collection (GC) cycle.
With this fix, the refcount on tail objects is no longer decremented when completing a copy-to-self.
|
Story Points: | --- |
| Clone Of: | 2356678 | Environment: | |
| Last Closed: | 2025-05-28 13:19:30 UTC | Type: | --- |
| 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: | 2356678 | ||
| Bug Blocks: | |||
|
Description
Bipin Kunal
2025-05-15 17:44:03 UTC
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 (Red Hat Ceph Storage 8.0 bug fix updates), 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/RHBA-2025:8259 |