Bug 129051 - lock_dlm: init_fence error -1
Summary: lock_dlm: init_fence error -1
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: gfs
Version: 4
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: David Teigland
QA Contact: Cluster QE
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-03 15:28 UTC by SEINGUERLET Patrick
Modified: 2010-01-12 02:55 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2004-08-19 05:05:57 UTC

Attachments (Terms of Use)

Description SEINGUERLET Patrick 2004-08-03 15:28:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
When I would like to mount the GFS file system, this messages appear. 
What can I do?

mount -t gfs /dev/test_gfs/lv_test /mnt
lock_dlm: init_fence error -1
GFS: can't mount proto = lock_dlm, table = test:partage1, hostdata =
mount: permission denied

I use a debian and I use the documentation file for install.


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

How reproducible:

Steps to Reproduce:

Additional info:

Comment 1 Derek Anderson 2004-08-03 15:32:50 UTC
1. Make sure you have cluster quorum. 
2. Join the default fence domain. 

Comment 2 SEINGUERLET Patrick 2004-08-03 15:43:13 UTC
Thanks, but how can I do this?

Thanks for all.

Comment 3 David Teigland 2004-08-19 05:05:57 UTC
This explains how to use these things:

The problem you see may be caused by having old/broken libraries
hanging around from a previous install.  Go through and remove all
libraries from all lib dirs from previous installs (libccs, libdlm,
libmagma, magma plugins), then reinstall everything.

Comment 4 Kiersten (Kerri) Anderson 2004-11-16 19:05:00 UTC
Updating version to the right level in the defects.  Sorry for the storm.

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