Bug 1065551

Note - /gluster is a directory on /, it's not it's own volume.

--

[root@rhel1 ~]# df /gluster/vol1
Filesystem     1K-blocks   Used Available Use% Mounted on
/dev/sda3       19325952 902340  18423612   5% /

[root@rhel2 ~]# df /gluster/vol1
Filesystem     1K-blocks   Used Available Use% Mounted on
/dev/sda3       19325952 903156  18422796   5% /

[root@rhel3 ~]# df /gluster/vol1
df: '/gluster/vol1': No such file or directory

[root@rhel4 ~]# df /gluster/vol1
df: '/gluster/vol1': No such file or directory

i tried this on a centos 6.5 host to make sure it's not isolated to rhel 7-beta and got the same behavior.

i discovered how to fix the actual brick add problem - i created a new physical disk and mounted it on /gluster, at that point adding the new bricks to my volume worked fine.

--

there is still one problem - the actual failure on the cli was not shown.  this should definitely be fixed.

contents of rhel1:/var/log/gluster/etc-glusterfs-glusterd.vol.log:

[2014-02-18 16:33:55.591046] I [glusterd-brick-ops.c:370:__glusterd_handle_add_brick] 0-management: Received add brick req
[2014-02-18 16:33:55.591185] I [glusterd-brick-ops.c:417:__glusterd_handle_add_brick] 0-management: replica-count is 2

contents of rhel3:/var/log/gluster/etc-glusterfs-glusterd.vol.log:

[2014-02-18 16:33:54.406180] E [glusterd-op-sm.c:3719:glusterd_op_ac_stage_op] 0-management: Stage failed on operation 'Volume Add brick', Status : -1

--

another issue: there is a typo here, "is is" should be "is"

volume create: vol1: failed: The brick rhel1:/gluster/vol1 is is being created in the root partition. It is recommended that you don't use the system's root partition for storage backend. Or use 'force' at the end of the command if you want to override this behavior.

REVIEW: http://review.gluster.org/7198 (glusterd: Fixed typo in console message during volume create) posted (#1) for review on master by Satheesaran Sundaramoorthi (satheesaran)

I have tried the first issue with centos 6.5
And I get the appropriate error messages,
[root@my-centos gluster-rpms]# gluster volume create repvol replica 2 192.168.122.31:/exp/1 192.168.122.31:/exp/2 force
Multiple bricks of a replicate volume are present on the same server. This setup is not optimal.
Do you still want to continue creating the volume?  (y/n) y
volume create: repvol: success: please start the volume to access data

[root@my-centos gluster-rpms]# gluster volume start repvol
volume start: repvol: success
[root@my-centos gluster-rpms]# gluster volume add-brick repvol replica 2 192.168.122.31:/exp/3 192.168.122.31:/exp/4
volume add-brick: failed: The brick 192.168.122.31:/exp/3 is is being created in the root partition. It is recommended that you don't use the system's root partition for storage backend. Or use 'force' at the end of the command if you want to override this behavior.

[root@my-centos gluster-rpms]# rpm -qa | grep gluster
glusterfs-fuse-3.4.2-1.el6.x86_64
glusterfs-libs-3.4.2-1.el6.x86_64
glusterfs-server-3.4.2-1.el6.x86_64
glusterfs-cli-3.4.2-1.el6.x86_64
glusterfs-rdma-3.4.2-1.el6.x86_64
glusterfs-3.4.2-1.el6.x86_64

For the typo in the error message, I have sent a patch here :
http://review.gluster.org/#/c/7198/


I couldn't reproduce the first issue

COMMIT: http://review.gluster.org/7198 committed in master by Vijay Bellur (vbellur) 
------
commit f1c4c9e6d47b637939b62b473178e1c3095651fc
Author: Satheesaran <satheesaran>
Date:   Thu Mar 6 15:40:31 2014 +0530

    glusterd: Fixed typo in console message during volume create
    
    While creating a volume, if the brick is created on the root
    partition, then the error statement is thrown.
    
    This error statements was containing two "is" in it.
    Removed one of the "is"
    
    Change-Id: I0d83f0feccda34989f7e2b97041d1f15ec9e2f00
    BUG: 1065551
    Signed-off-by: Satheesaran <satheesaran>
    Reviewed-on: http://review.gluster.org/7198
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Reviewed-by: Vijay Bellur <vbellur>

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

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-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users