Skip to content

Commit

Permalink
Do not create brick dir before creating volume (#761)
Browse files Browse the repository at this point in the history
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
  • Loading branch information
tnyeanderson authored Jul 31, 2023
1 parent c9eff98 commit ce1e76a
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion docs/Install-Guide/Configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down

0 comments on commit ce1e76a

Please sign in to comment.