From ce1e76a67ce0d93a8edd845bdc4f0df69a687d9a Mon Sep 17 00:00:00 2001 From: Thomas Anderson Date: Sun, 30 Jul 2023 23:50:22 -0400 Subject: [PATCH] Do not create brick dir before creating volume (#761) If the brick directory is already present on the machine, you may get the error `volume create: g: failed: 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 --- docs/Install-Guide/Configure.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/Install-Guide/Configure.md b/docs/Install-Guide/Configure.md index 9d475d97..9bad7523 100644 --- a/docs/Install-Guide/Configure.md +++ b/docs/Install-Guide/Configure.md @@ -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 ` 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