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:
tunegfs2 is a tune2fs work-a-like for GFS2. It should probably be located in the same directory.
tune2fs is located in /sbin
tunegfs2 is located in /usr/sbin
tunegfs2 doesn't depend on any libraries in /usr so it could be moved to /sbin.
[root@buzz-02 sbin]# ldd /usr/sbin/tunegfs2
linux-vdso.so.1 => (0x00007fff3f5ff000)
libc.so.6 => /lib64/libc.so.6 (0x00000031c9400000)
/lib64/ld-linux-x86-64.so.2 (0x00000031c8c00000)
Version-Release number of selected component (if applicable):
gfs2-utils-3.0.12.1-5.el6.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. which tunegfs2
2.
3.
Actual results:
# which tunegfs2
/usr/sbin/tunegfs2
Expected results:
# which tunegfs2
/sbin/tunegfs2
Additional info:
Well, the FHS says:
/sbin contains binaries essential for booting, restoring, recovering, and/or repairing the system in addition to the binaries in /bin. [18] Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin.
So bearing in mind that tunegfs2 shouldn't be needed for mounting the fs or recovering it, and we don't support gfs2 on root anyway, I'm not sure that this is a bug. I know we could move it, but I'm not convinced that it is in the wrong place, even if tune2fs is in /sbin.
Description of problem: tunegfs2 is a tune2fs work-a-like for GFS2. It should probably be located in the same directory. tune2fs is located in /sbin tunegfs2 is located in /usr/sbin tunegfs2 doesn't depend on any libraries in /usr so it could be moved to /sbin. [root@buzz-02 sbin]# ldd /usr/sbin/tunegfs2 linux-vdso.so.1 => (0x00007fff3f5ff000) libc.so.6 => /lib64/libc.so.6 (0x00000031c9400000) /lib64/ld-linux-x86-64.so.2 (0x00000031c8c00000) Version-Release number of selected component (if applicable): gfs2-utils-3.0.12.1-5.el6.x86_64 How reproducible: Every time Steps to Reproduce: 1. which tunegfs2 2. 3. Actual results: # which tunegfs2 /usr/sbin/tunegfs2 Expected results: # which tunegfs2 /sbin/tunegfs2 Additional info: