Bug 112621

Summary:	(JFS) Description text in rpm details commands that are not included
Product:	Red Hat Enterprise Linux 3	Reporter:	Bryan <bryan>
Component:	jfsutils	Assignee:	Jeff Garzik <jgarzik>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	peterm
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 19:31:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bryan 2003-12-24 19:15:11 UTC

Description of problem:

The Description text produced by an 'rpm -qi' says that:

"The following utilities are available: fsck.jfs - initiate
replay of the JFS transaction log, and check and repair a JFS
formatted device; logdump - dump a JFS formatted device's journal log;
logredo - "replay" a JFS formatted device's journal log;  mkfs.jfs -
create a JFS formatted partition; xchkdmp - dump the contents of a JFS
fsck log file created with xchklog; xchklog - extract a log from the
JFS fsck workspace into a file;  xpeek - shell-type JFS file system
editor."

The package does *not* include the logredo, xchkdmp, xchklog, or xpeek
commands.

Additional info:

These same commands are also missing from the Fedora package.
These commands are present in the RH9 package.

Comment 1 Jeff Garzik 2004-03-03 08:23:42 UTC

Is this still the case with the latest jfsutils package in rawhide?

Comment 2 RHEL Program Management 2007-10-19 19:31:56 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.