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:

I saw in RHEL 7.4 in "man mkfs.xfs" 

If you go down to the part where ftype is mentioned: 

the spelling for "signifying" is wrong, could we please fix this? 

~~~
                   ftype=value
                          ::
                          The value is either 0 or 1, with 1 signifiying  that
                          filetype information will be stored in the directory
                          structure. The default value is 0.
                          ::
~~~

I think this typo error is not so important, but if we'd like to fix it, maybe backport this commit, then this typo error can be fixed together?

commit f10a5ab0b3a4cb8a7e17a4935fb33d283c3dd31f
Author: Eric Sandeen <sandeen>
Date:   Tue Sep 20 08:48:54 2016 +1000

    mkfs.xfs: clarify ftype defaults in manpage

Its not important, if possible we can fix it, but it can be left as it is for later times.

We're updating xfsprogs for other bugs anyway, and the upstream commit which fixes it fixes technical inaccuracies as well, so it's worth doing now I think.

Thanks,
-Eric

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, 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-2018:0847