Description of problem: 1. gluster volume create with spaces in directory in brick path fails. 2. If you run the same command with quotes for brick, it misunderstands brick path and creates a directory with escape character Version-Release number of selected component (if applicable): How reproducible: # gluster volume create tv2 gfvm2:/opt/volume_test/tv_1/b\ 1 force volume create: tv2: failed: Brick: gfvm2:/opt/volume_test/tv_1/b not available. Brick may be containing or be contained by an existing brick # gluster volume create tv2 "gfvm2:/opt/volume_test/tv_1/b\ 1" force volume create: tv2: success: please start the volume to access data # gluster volume info tv2 Volume Name: tv2 Type: Distribute Volume ID: 6e07a8f5-6564-4951-8398-3b65825385bc Status: Created Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: gfvm2:/opt/volume_test/tv_1/b\ Options Reconfigured: performance.readdir-ahead: on Steps to Reproduce: 1.gluster volume create tv2 gfvm2:/opt/volume_test/tv_1/b\ 1 force 2.gluster volume create tv2 "gfvm2:/opt/volume_test/tv_1/b\ 1" force 3. Actual results: Errors as given above Expected results: 1. If space is NOT accepted in brick path, it should be displayed properly. 2. I think escape character should NOT be used for creating a Brick.(as mentioned in gluster info <volume>) before. Additional info:
This remains as a bug, but fixing this currently is not a priority among other things. It would become a major work, as everywhere we take brick as argument, we need to handle space. We will add this in documentation, and mark this bug as DEFERRED, so we can revisit this after couple of releases.