RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Because of https://bugzilla.redhat.com/show_bug.cgi?id=1623150, xfs will disable per-inode DAX enablement. So after the patches for bz1623150 applied, "chattr +/-x" in xfs_io will can't work. So I file this bug to evaluate if this function will removed in RHEL-7.6 or RHEL-7.7. Maybe RHEL-7.7 is better.

Version-Release number of selected component (if applicable):
xfsprogs-4.5.0-18.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

This may worth doing it.

Ok, yes.  The kernel will not set or query the dax flag; it knows nothing at all about it.  So I can just remove all references to +/-x from xfs_io and the manpage as well.

(I was thinking I needed to still display it and/or allow removal, but even if the flag exists on disk the kernel will not report it, so there is no way to remove it, and it's ignored in any case)

I have a fix staged for this, but I'll need a qe ack.  Would you like me to proceed?

it removes +/-x, but that will cause an fstests failure.  I sent a patch upstream to detect if a flag is not available, and skip the test.

xfsprogs-4.5.0-22.el7 has removed FS_XFLAG_DAX flag. And I can't find anything about 'x' option from lsattr and chattr man-page and help output.

# xfs_io -c 'help lsattr'
# xfs_io -c 'help chattr'
# man xfs_ioh

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 (xfsprogs bug fix and enhancement update), 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-2020:4028