Bug 763444 (GLUSTER-1712) - Error is not logged for a dangling volume
Summary: Error is not logged for a dangling volume
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1712
Product: GlusterFS
Classification: Community
Component: core
Version: nfs-beta
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-27 07:11 UTC by Sachidananda Urs
Modified: 2015-12-01 16:45 UTC (History)
3 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)

Description Sachidananda Urs 2010-09-27 07:11:52 UTC
If I start glusterfs with a volume file like:

volume posix1
    type storage/posix
#   option o-direct enable # (default: disable) boolean type only
#   option export-statfs-size no # (default: yes) boolean type only
#   option mandate-attribute off # (default: on) boolean type only
#   option span-devices 8 # (default: 0) integer value
#   option background-unlink yes # (default: no) boolean type
    option directory /exports/nfs
end-volume

volume posix-ac1
    type features/access-control
    subvolumes posix1
end-volume

volume locks1
    type features/locks
#   option mandatory on # Default off, used in specific applications
    subvolumes posix1
end-volume

================
Error should be logged saying posix-ac1 is dangling, and if access-control is mandatory then GlusterFS should not start.

Instead GlusterFS starts with no errors. i.e starts without access-control.

Comment 1 Vijay Bellur 2010-09-28 08:50:44 UTC
PATCH: http://patches.gluster.com/patch/4994 in master (access-control: report possible errors in graph during 'init()')


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