Bug 189221

Summary:	lockspace in use error could be more helpful
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Corey Marthaler <cmarthal>
Component:	gfs	Assignee:	David Teigland <teigland>
Status:	CLOSED CURRENTRELEASE	QA Contact:	GFS Bugs <gfs-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	GFS-6.1.6-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-11-07 18:06:13 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 Corey Marthaler 2006-04-18 14:21:45 UTC

Description of problem:
I created two gfs file systems with the exact same locktable and then attempted
to mount them one after another. The error I got for the second mount attempt
could be much more helpful.

[root@link-02 ~]# mount -t gfs /dev/link/link1 /mnt/link1
mount: File exists
[root@link-02 ~]# echo $?
32

"lockspace already in use" or something to that affect would be nicer. :)

Even /var/log/messages wasn't that much more helpful:

GFS: Trying to join cluster "lock_dlm", "LINK_CLUSTER:link1"
lock_dlm: new lockspace error -17
GFS: can't mount proto = lock_dlm, table = LINK_CLUSTER:link1, hostdata =
Apr 17 14:55:41 link-03 kernel: GFS: Trying to join cluster "lock_dlm",
"LINK_CLUSTER:link1"
Apr 17 14:55:41 link-03 kernel: lock_dlm: new lockspace error -17
Apr 17 14:55:41 link-03 kernel: GFS: can't mount proto = lock_dlm, table =
LINK_CLUSTER:link1, hostdata =


Version-Release number of selected component (if applicable):
[root@link-02 ~]# rpm -qa GFS
GFS-6.1.5-0

Comment 1 David Teigland 2006-04-18 14:50:38 UTC

Added log_error(ls, "lockspace already in use");
There's no way to report our own error messages
from mount(8).

Comment 2 Corey Marthaler 2006-11-07 18:06:13 UTC

fix verified.