Description of problem:
A user created a volume using /var/lib/glusterd/vols/brick assuming that the structure was named that way to be the brick.
The working-directory configured in the should be disallowed from having bricks under it.
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.
If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.
Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.
Gaurav - do you mind sending a patch for this? The fix should be straight forward. In the brick path validation code path we'd need to do an strstr of the brick path and glusterd workdir.
REVIEW: https://review.gluster.org/21066 (glusterd: avoid using /var/lib/glusterd as a brick) posted (#1) for review on master by Sanju Rakonde
COMMIT: https://review.gluster.org/21066 committed in master by "Sanju Rakonde" <firstname.lastname@example.org> with a commit message- glusterd: avoid using glusterd's working directory as a brick
Adding checks for avoiding glusterd's working directory used as
a brick for volume creation.
Signed-off-by: Sanju Rakonde <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.
glusterfs-5.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.