This bug was initially created as a copy of Bug #2267715 I am copying this bug because: Description of problem: Based on the experience from the field the "/usr/bin/rgw-restore-bucket-index" tool stores temporary objects in /tmp directory, these objects consumes space based on the size of the bucket that is being recovered, for large buckets this can eventually lead to "/usr/bin/rgw-restore-bucket-index" tool failure due to running out of space, but the error message does not suggest that is the case, but rather fails with "ln: failed to access '/tmp/rgwrbi-object-list.XXX': No such file or directory" With that information, would it make sense to consider 2 improvements of the "/usr/bin/rgw-restore-bucket-index" tool: 1. add option for custom path where the files will be stored 2. add detection of running out of space Version-Release number of selected component (if applicable): RHCS 5, 6, 7 How reproducible: always Steps to Reproduce: 1. have 4GB large /tmp 2. attempt to recover bucket with 17M objects Actual results: Expected results: Additional info:
Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
Waiting for 6.1z5 to go out the door before cherry-picking two commits.
We need to pull the commits from 2 upstream PRs: https://github.com/ceph/ceph/pull/55885 https://github.com/ceph/ceph/pull/56133
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 6.1 security, bug fix, and enhancement 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-2024:5960