Bug 853601 - working-directory should be protected from being a brick [NEEDINFO]
working-directory should be protected from being a brick
Status: NEW
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
: Reopened, Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-09-01 02:40 EDT by Joe Julian
Modified: 2018-03-29 18:08 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-03-08 06:04:53 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
amukherj: needinfo? (gyadav)

Attachments (Terms of Use)

  None (edit)
Description Joe Julian 2012-09-01 02:40:07 EDT
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.
Comment 1 Kaleb KEITHLEY 2015-10-22 11:46:38 EDT
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.
Comment 3 Kaushal 2017-03-08 06:04:53 EST
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.
Comment 4 Atin Mukherjee 2017-08-15 10:40:43 EDT
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.

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