Description of problem: When we try to create volume with bricks in root partition, gluster cli will give following error. But it creates volume successfully in script mode. gluster volume create gv1 sumne.sumne:/gfs/gv1_b1 sumne.sumne:/gfs/gv1_b2 volume create: gv1: failed: The brick sumne.sumne:/gfs/gv1_b1 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. How reproducible: 100% Steps to Reproduce: 1. Create volume with bricks dir in root partition gluster volume create gv1 sumne.sumne:/gfs/gv1_b1 sumne.sumne:/gfs/gv1_b2 It will fail with above mentioned error 2. Create volume with script mode gluster volume create gv1 sumne.sumne:/gfs/gv1_b1 sumne.sumne:/gfs/gv1_b2 --mode=script Creates volume successfully. Actual results: Creates volume successfully without any error. Expected results: Script mode should fail if brick dirs are system's root partition.
REVIEW: http://review.gluster.org/6409 (cli: Fail creation of bricks on root partition in script mode) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/6409 committed in master by Anand Avati (avati) ------ commit def8890d5ea7e73dfa37023e5d324be0bc289f5a Author: Krutika Dhananjay <kdhananj> Date: Mon Dec 2 11:37:55 2013 +0530 cli: Fail creation of bricks on root partition in script mode Also added an option 'wignore' to save ourselves the trouble of modifying test scripts in our regression test suite as well as those that are still under review. Change-Id: Id320c03595506e9da187e766991c19640bd000c5 BUG: 1028281 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/6409 Reviewed-by: Kaushal M <kaushal> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
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