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:
Please, update xfs_io man page to include documentation for the following commands:
chproj
lsproj
setfl
Version-Release number of selected component (if applicable):
xfsprogs-3.1.1-10.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Run xfstests test no. 293 that checks for this behaviour.
2.
3.
Actual results:
The test fails reporting the missing documentation for the threee commands.
Expected results:
The commands are documented.
Additional info:
The test case seems to be written by Eric Sandeen. Hence, I searched the bugzilla for a similar report. However, I didn't find any RHEL 6 report for this lack of documentation.
xfs_io -c help already provides basic documentation for the three commands:
chproj [-D | -R] projid -- change project identifier on the currently open file
lsproj [-D | -R] -- list project identifier set on the currently open file
setfl [-adx] -- set/clear append/direct flags on the open file
commit 83c324088f8e60133016409752b08f74e19e8b37
Author: Eric Sandeen <sandeen>
Date: Sat Dec 8 20:55:18 2012 +0000
xfsprogs: document all commands in xfs_io
Add missing command documentation to xfs_io(8) manpage.
fiemap, fpunch, chproj, lsproj, and setfl are all missing.
setfl seems to not work today in any case, and nothing
in xfstests uses it; I will send another patch to simply
remove it from xfs_io, as I don't think it's terribly useful,
and hasn't worked forever anyway.
Also fix references to the fallocate manpage, which is (now?)
in section 2, not section 3 of the man pages. (Since it's
a syscall, not a library function).
Signed-off-by: Eric Sandeen <sandeen>
commit 618e842d3553d24e7ba2c740a080ab6f972868c6
Author: Eric Sandeen <sandeen>
Date: Sat Dec 8 21:03:10 2012 +0000
xfsprogs: remove setfl from xfs_io
Doesn't seem to have worked for ages, and is (therefore)
apparently not ever used:
xfs_io> setfl
xfs_io> help setfl
setfl [-adx] -- set/clear append/direct flags on the open file
xfs_io> setfl -a
bad argument count 1 to setfl, expected 0 arguments
xfs_io> setfl -d
bad argument count 1 to setfl, expected 0 arguments
xfs_io> setfl
xfs_io>
At best, it seems intended to toggle the flag state, but
gives no feedback about current state. -x is in help but
not implemented, etc.
Just remove it.
Signed-off-by: Eric Sandeen <sandeen>
Reviewed-by: Carlos Maiolino <cmaiolino>
Signed-off-by: Mark Tinguely <tinguely>
If we are allowed to update xfsprogs in 6.5 it'd be easy to include these 2 commits.
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.
http://rhn.redhat.com/errata/RHBA-2013-1657.html