Description of problem: The man page for the gfs2_tool command notes that the jdata and inherit_jdata flags are now set with chattr. Just as described, the gfs2_tool setflag command no longer accepts the inherit_jdata option. However, it does accept the jdata option, and even seems to set the jdata flag just fine. It seems as though the jdata flag should no longer be valid at all for the gfs2_tool setflag command, just as the man page says. Version-Release number of selected component (if applicable): How reproducible: Execute gfs2_tool setflag jdata on a file. This will yield no error message. Execute lsattr on that file. This will show that the flag has been set. [root@dash-01 mygfs2fs]# gfs2_tool setflag jdata /mygfs2fs/data [root@dash-01 mygfs2fs]# lsattr data ---------j--- data/foo Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I've got a replacement man page that explains this better. Requesting ack flags for inclusion in RHEL5.2.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Created attachment 250851 [details] patch to fix the problem
Updated man page committed to cvs at HEAD and RHEL5 branches for inclusion in RHEL5.2. Changing status to Modified.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0350.html