| Summary: | Error is not logged for a dangling volume | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sachidananda Urs <sac> |
| Component: | core | Assignee: | Amar Tumballi <amarts> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | nfs-beta | CC: | amarts, gluster-bugs, vraman |
| 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: | |
PATCH: http://patches.gluster.com/patch/4994 in master (access-control: report possible errors in graph during 'init()') |
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.