Bug 2392403 - [ganesha][RFE] subvolume quotas not passed to the nfs client
Summary: [ganesha][RFE] subvolume quotas not passed to the nfs client
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: NFS-Ganesha
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 8.1z3
Assignee: Frank Filz
QA Contact: sumr
Rivka Pollack
URL:
Whiteboard:
Depends On: 2248613
Blocks: 2389764
TreeView+ depends on / blocked
 
Reported: 2025-09-01 14:48 UTC by Manisha Saini
Modified: 2025-09-30 09:23 UTC (History)
19 users (show)

Fixed In Version: ceph-19.2.1-261.el9cp; nfs-ganesha-6.5-27.el9cp
Doc Type: Enhancement
Doc Text:
.Enhanced quota reporting for CephFS subvolumes exported with NFS-Ganesha Previously, when CephFS subvolumes were created with a quota and exported using NFS-Ganesha, NFS clients incorrectly reported the full volume size, instead of the quota-defined size. As a result, this behavior could lead to unexpected write failures, which were difficult to diagnose from the client side. With this enhancement, the NFS client now correctly reports the quota size of the subvolume. When the quota is exceeded, standard error handling as 'Disk quota exceeded' occurs.
Clone Of: 2248613
Environment:
Last Closed: 2025-09-30 09:23:12 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-12040 0 None None None 2025-09-01 14:48:57 UTC
Red Hat Product Errata RHBA-2025:17047 0 None None None 2025-09-30 09:23:21 UTC

Description Manisha Saini 2025-09-01 14:48:09 UTC 
+++ This bug was initially created as a clone of Bug #2248613 +++
Comment 10 errata-xmlrpc 2025-09-30 09:23:12 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.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-2025:17047
Note You need to log in before you can comment on or make changes to this bug.