Bug 2345288 - ceph.quota.max_bytes accepting Values like TG, GT, KT
Summary: ceph.quota.max_bytes accepting Values like TG, GT, KT
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 8.1
Assignee: Neeraj Pratap Singh
QA Contact: Manimaran M
Rivka Pollack
URL:
Whiteboard:
Depends On: 2345555 2299816
Blocks: 2344791 2351689
TreeView+ depends on / blocked
 
Reported: 2025-02-12 16:49 UTC by Greg Farnum
Modified: 2025-06-26 12:25 UTC (History)
10 users (show)

Fixed In Version: 19.2.1-56.el9cp
Doc Type: Enhancement
Doc Text:
.`quota.max_bytes` is now set in more understandable size values Previously, the `quota.max_bytes` value was set in bytes, resulting in often very large size values, which were hard to set or change. With this enhancement, the `quota.max_bytes` values can now be set with human-friendly values, such as M/Mi, G/Gi, or T/Ti. For example, 10GiB or 100K.
Clone Of: 2299816
Environment:
Last Closed: 2025-06-26 12:25:33 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 67169 0 None None None 2025-03-21 10:33:42 UTC
Red Hat Issue Tracker RHCEPH-10605 0 None None None 2025-02-12 16:50:04 UTC
Red Hat Product Errata RHSA-2025:9775 0 None None None 2025-06-26 12:25:47 UTC

Description Greg Farnum 2025-02-12 16:49:04 UTC 
+++ This bug was initially created as a clone of Bug #2299816 +++
Comment 15 errata-xmlrpc 2025-06-26 12:25:33 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 (Important: Red Hat Ceph Storage 8.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/RHSA-2025:9775
Note You need to log in before you can comment on or make changes to this bug.