Bug 2297166 - setfattr -x option is not working for ceph.quota.maxfiles [NEEDINFO]
Summary: setfattr -x option is not working for ceph.quota.maxfiles
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: Rishabh Dave
QA Contact: Amarnath
Rivka Pollack
URL:
Whiteboard:
Depends On:
Blocks: 2351689
TreeView+ depends on / blocked
 
Reported: 2024-07-10 17:38 UTC by Amarnath
Modified: 2025-06-26 12:14 UTC (History)
10 users (show)

Fixed In Version: ceph-19.2.1-37.el9cp
Doc Type: Bug Fix
Doc Text:
Expanded `removexattr` support for CephFS virtual extended attributes Previously, `removexattr` was not supported on all appropriate Ceph virtual extended attributes, resulting in attempts to remove an extended attribute failing with a "No such attribute" error. With this fix, support for `removexattr` has been expanded to cover all pertinent CephFS virtual extended attributes. You can now properly use `removexattr` to remove attributes. You can also remove the layout on the root inode. Removing the layout restores the configuration to the default layout.
Clone Of:
Environment:
Last Closed: 2025-06-26 12:13:59 UTC
Embargoed:
gfarnum: needinfo? (vshankar)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 62793 0 None None None 2025-04-03 06:11:23 UTC
Red Hat Issue Tracker RHCEPH-9306 0 None None None 2024-07-10 17:39:41 UTC
Red Hat Product Errata RHSA-2025:9775 0 None None None 2025-06-26 12:14:08 UTC

Description Amarnath 2024-07-10 17:38:48 UTC
Description of problem:
setfattr -x option is not working for ceph.quota.maxfiles

added extended attribute to directory. when we did get it worked but when we did setfattr -x it fails with "No such attribute"

[root@ceph-amk-regression-oz3229-node7 ceph_kernel]# getfattr -n ceph.quota.max_files  /mnt/ceph_kernel/file_srcdir/ceph-amk-regression-oz3229-node7/thrd_00/d_000
getfattr: Removing leading '/' from absolute path names
# file: mnt/ceph_kernel/file_srcdir/ceph-amk-regression-oz3229-node7/thrd_00/d_000
ceph.quota.max_files="100"

[root@ceph-amk-regression-oz3229-node7 ceph_kernel]# setfattr -x ceph.quota.max_files  /mnt/ceph_kernel/file_srcdir/ceph-amk-regression-oz3229-node7/thrd_00/d_000
setfattr: /mnt/ceph_kernel/file_srcdir/ceph-amk-regression-oz3229-node7/thrd_00/d_000: No such attribute


This is happening on both fuse and kernel mounts


Version-Release number of selected component (if applicable):
[root@ceph-amk-regression-oz3229-node7 ceph_kernel]# ceph versions
{
    "mon": {
        "ceph version 18.2.1-215.el9cp (07fe9c7b0b710d1ee1e5a4a796a70d32bdb8664e) reef (stable)": 3
    },
    "mgr": {
        "ceph version 18.2.1-215.el9cp (07fe9c7b0b710d1ee1e5a4a796a70d32bdb8664e) reef (stable)": 2
    },
    "osd": {
        "ceph version 18.2.1-215.el9cp (07fe9c7b0b710d1ee1e5a4a796a70d32bdb8664e) reef (stable)": 12
    },
    "mds": {
        "ceph version 18.2.1-215.el9cp (07fe9c7b0b710d1ee1e5a4a796a70d32bdb8664e) reef (stable)": 4
    },
    "overall": {
        "ceph version 18.2.1-215.el9cp (07fe9c7b0b710d1ee1e5a4a796a70d32bdb8664e) reef (stable)": 21
    }
}


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Storage PM bot 2024-07-10 17:39:01 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 17 errata-xmlrpc 2025-06-26 12:13:59 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.