gluster/glusterdocs
1
0
Fork 0
mirror of https://github.com/gluster/glusterdocs.git synced 2026-02-05 15:47:01 +01:00
Code Issues Releases Activity

Do not create brick dir before creating volume (#761)

Browse Source 
If the brick directory is already present on the machine, you may get the error `volume create: g: failed: <brick> is already part of a volume` when running `volume create`. Stack overflow comment which pointed out the error:

https://stackoverflow.com/questions/39446546/glusterfs-volume-creation-failed-brick-is-already-part-of-volume#comment124667244_41575330
This commit is contained in:
Thomas Anderson
2023-07-30 23:50:22 -04:00
committed by GitHub
parent c9eff98ed3
commit ce1e76a67c
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Install-Guide/Configure.md
View File

@@ -53,7 +53,7 @@ echo "/dev/sdb1 /export/sdb1 xfs defaults 0 0" >> /etc/fstab
### Mount the partition as a Gluster "brick"
```console
mkdir -p /export/sdb1 && mount -a && mkdir -p /export/sdb1/brick
mkdir -p /export/sdb1 && mount -a
```
#### Set up a Gluster volume
@@ -87,6 +87,8 @@ Breaking this down into pieces:
means each server will house a copy of the data.
- we specify which nodes to use, and which bricks on those nodes. The order here is
important when you have more bricks.
- the brick directory will be created by this command. If the directory already
exists, you may get `<brick> is already part of a volume` errors.
It is possible (as of the most current release as of this writing, Gluster 3.3)
to specify the bricks in such a way that you would make both copies of the data reside on a