Bug 1715946 - [RGW-NFS]: objects stored on nfs mount may have inconsistent tail tag and fail to gc
Summary: [RGW-NFS]: objects stored on nfs mount may have inconsistent tail tag and fai...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.2
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: 3.3
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2019-05-31 17:31 UTC by Matt Benjamin (redhat)
Modified: 2019-08-21 15:11 UTC (History)
9 users (show)

Fixed In Version: RHEL: ceph-12.2.12-15.el7cp Ubuntu: ceph_12.2.12-14redhat1
Doc Type: Bug Fix
Doc Text:
.Space is no longer leaked when deleting objects via NFS Previously, the Ceph Object Gateway NFS implementation incorrectly set a value used to construct a key subsequently used to set garbage collection (GC) on shadow objects. Deleting an object via NFS, as opposed to S3 or Swift, could cause space to be leaked. With this update, the GC tag is now set correctly and space is not leaked when deleting objects via NFS.
Clone Of:
Environment:
Last Closed: 2019-08-21 15:11:09 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 37734 0 None None None 2019-05-31 17:31:37 UTC
Red Hat Product Errata RHSA-2019:2538 0 None None None 2019-08-21 15:11:26 UTC

Description Matt Benjamin (redhat) 2019-05-31 17:31:38 UTC 
Description of problem:
The logic for associating RGW request id tokens with tail objects was broken by NFS mapping of writes to multiple "continued requests."  This could cause objects with tail chunks to fail to gc after deletion.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
See upstream tracker.
Comment 13 errata-xmlrpc 2019-08-21 15:11:09 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, 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-2019:2538
Note You need to log in before you can comment on or make changes to this bug.