Bug 762436 (GLUSTER-704) - GlusterFS starts despite error is logged in GlusterFS
Summary: GlusterFS starts despite error is logged in GlusterFS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-704
Product: GlusterFS
Classification: Community
Component: core
Version: 3.0.2
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-08 14:03 UTC by Sachidananda Urs
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.)
Note You need to log in before you can comment on or make changes to this bug.