Bug 762436 (GLUSTER-704)

Summary:	GlusterFS starts despite error is logged in GlusterFS
Product:	[Community] GlusterFS	Reporter:	Sachidananda Urs <sac>
Component:	core	Assignee:	Anand Avati <aavati>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.0.2	CC:	amarts, chrisw, gluster-bugs, vijay
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:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sachidananda Urs 2010-03-08 14:03:19 UTC

When GlusterFS is started with option mandatory-locks, error is logged in the log file:

--snip--

[2010-03-08 13:58:49] E [posix.c:1477:init] brick4: mandatory locks not supported in this minor release.
[2010-03-08 13:58:49] E [posix.c:1477:init] brick3: mandatory locks not supported in this minor release.
[2010-03-08 13:58:49] E [posix.c:1477:init] brick2: mandatory locks not supported in this minor release.
[2010-03-08 13:58:49] E [posix.c:1477:init] brick1: mandatory locks not supported in this minor release.
[2010-03-08 13:58:49] N [glusterfsd.c:1396:main] glusterfs: Successfully started

--snip--

Despite that GlusterFS is started.
If error is logged then GlusterFS should not be started, else the messages have to be logged as warning.

Comment 1 Anand Avati 2010-03-12 09:09:45 UTC

PATCH: http://patches.gluster.com/patch/2879 in master (When option mandatory is given, print warning messages instead of Error.)

Comment 2 Anand Avati 2010-03-12 09:09:49 UTC

PATCH: http://patches.gluster.com/patch/2880 in release-3.0 (When option mandatory is given, print warning messages instead of Error.)