Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 311591 - RFE: make lock_dlm the default mkfs lockproto
RFE: make lock_dlm the default mkfs lockproto
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gfs-utils (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Abhijith Das
GFS Bugs
: Documentation
Depends On:
Blocks: 435917
  Show dependency treegraph
Reported: 2007-09-28 15:07 EDT by Corey Marthaler
Modified: 2010-01-11 22:33 EST (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2008-0349
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-21 10:36:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0349 normal SHIPPED_LIVE gfs-utils bug fix update 2008-05-20 08:50:54 EDT

  None (edit)
Description Corey Marthaler 2007-09-28 15:07:13 EDT
Description of problem:
Without lockgulm around in rhel5 anymore, it seems silly to have to enter a lock
protocol everytime I mkfs a new gfs filesystem.

From the man page:
"LockProtoName is the name of the  locking  protocol to use.  The locking
protocol should be lock_dlm for a clustered file system..."

Version-Release number of selected component (if applicable):
Comment 4 Abhijith Das 2007-10-17 16:17:52 EDT
committed fix to cvs HEAD and RHEL5 to make lock_dlm the default lock protocol
in mkfs.gfs and mkfs.gfs2.
Comment 6 Corey Marthaler 2007-12-19 17:05:48 EST
fixed verified in gfs-utils-0.1.15-1.el5.
Comment 8 errata-xmlrpc 2008-05-21 10:36:30 EDT
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.


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