Bug 222747 - Remove references to lock_gulm from cluster man pages
Remove references to lock_gulm from cluster man pages
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gfs-utils (Show other bugs)
5.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Robert Peterson
GFS Bugs
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-15 18:09 EST by Robert Peterson
Modified: 2010-01-11 22:32 EST (History)
3 users (show)

See Also:
Fixed In Version: RC
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-07 21:16:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Robert Peterson 2007-01-15 18:09:32 EST
Description of problem:
The man page for gfs_mount has references to lock_gulm which no longer
exists for RHEL5.  Also, it references "hostdata=" which says it doesn't
apply to dlm or nolock, so they should also be removed if no longer
applicable.

Version-Release number of selected component (if applicable):
RHEL5

How reproducible:
Always

Steps to Reproduce:
1. man gfs_mount
  
Actual results:
Man page references gulm locking protocol.

Expected results:
Man page should not reference gulm.

Additional info:
Reported by Steven Levine (thanks!)
Comment 2 Kiersten (Kerri) Anderson 2007-01-16 11:24:22 EST
Need to remove the reference to gulm, do not want to advertise this in rhel5.0.
 DEVEL ACK - and agreement from Dean Jansa for QA ack.
Comment 4 Benjamin Kahn 2007-01-16 11:38:08 EST
This is a RHEL 5 bug.
Comment 5 Robert Peterson 2007-01-16 14:23:41 EST
I found four man pages with references to lock_gulm: fence.8, gfs_mkfs.8,
gfs_mount.8, and gfs2_mount.8.  These parts have been fixed and checked 
in to CVS at HEAD, RHEL5 and RHEL50.  I also added some copyright notices 
where I noticed they were missing.
Comment 7 RHEL Product and Program Management 2007-02-07 21:16:25 EST
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.

Note You need to log in before you can comment on or make changes to this bug.