Bug 2317027 - BlueFS files take too much space
Summary: BlueFS files take too much space
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 8.0
Assignee: Adam Kupczyk
QA Contact: Harsh Kumar
URL:
Whiteboard:
Depends On:
Blocks: 2317044 2317218
TreeView+ depends on / blocked
 
Reported: 2024-10-07 18:05 UTC by Bipin Kunal
Modified: 2024-11-25 09:13 UTC (History)
8 users (show)

Fixed In Version: ceph-19.2.0-42.el9cp
Doc Type: Bug Fix
Doc Text:
.RocksDB files now only take as much space as needed Previously, RocksDB files were generously preallocated but never truncated. This resulted in wasted disk space that was assigned to files that would never be used. With this fix, proper truncation is implemented, moving unused allocations back to the free pool.
Clone Of:
: 2317044 (view as bug list)
Environment:
Last Closed: 2024-11-25 09:12:53 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-9931 0 None None None 2024-10-07 18:08:01 UTC
Red Hat Product Errata RHBA-2024:10216 0 None None None 2024-11-25 09:13:03 UTC

Description Bipin Kunal 2024-10-07 18:05:08 UTC
Description of problem: BlueFS files take too much space

Backport the fix https://tracker.ceph.com/issues/68385 to downstream.

Version-Release number of selected component (if applicable):
As per Adam the issue is seen with 7.1z1 and above.

Comment 16 errata-xmlrpc 2024-11-25 09:12:53 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 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:10216


Note You need to log in before you can comment on or make changes to this bug.