Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
deprecated/unimplemented function in man page exports(5):
'''
sync Reply to requests only after the changes have been committed to stable storage (see async above).
In releases of nfs-utils up to and including 1.0.0, the async option was the default. In all releases after 1.0.0, sync is the default, and async must be explicitly requested if needed. To help make system administrators aware of this change, exportfs will issue a warning if neither sync nor async is specified.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
'''
but actually exportfs does not issue any warning, if neither sync nor async is specified.
Version-Release number of selected component (if applicable):
all nfs-uitls version
How reproducible:
always
Steps to Reproduce:
1. systemctl start nfs-server
2. exportfs -orw *:/nfsshare
Actual results:
but actually exportfs does not issue any warning, if neither sync nor async is specified.
Expected results:
exportfs will issue a warning if neither sync nor async is specified.
Additional info:
Looks like Neil Brown removed that warning 16 years ago:
commit 6a7d90cea765
Author: Neil Brown <neilb>
Date: Mon Aug 7 14:19:32 2006 +1000
Remove warning if neither 'sync' or 'async' present.
He probably just forgot to update the man page. I guess the warning must have been meant to be a transitional thing. Updating the man page sounds like the right thing to me.
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 (nfs-utils 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-2021:1669
Description of problem: deprecated/unimplemented function in man page exports(5): ''' sync Reply to requests only after the changes have been committed to stable storage (see async above). In releases of nfs-utils up to and including 1.0.0, the async option was the default. In all releases after 1.0.0, sync is the default, and async must be explicitly requested if needed. To help make system administrators aware of this change, exportfs will issue a warning if neither sync nor async is specified. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ''' but actually exportfs does not issue any warning, if neither sync nor async is specified. Version-Release number of selected component (if applicable): all nfs-uitls version How reproducible: always Steps to Reproduce: 1. systemctl start nfs-server 2. exportfs -orw *:/nfsshare Actual results: but actually exportfs does not issue any warning, if neither sync nor async is specified. Expected results: exportfs will issue a warning if neither sync nor async is specified. Additional info: