Current error message for minimum size brick heketi-cli volume create --size=1 Error: No space [heketi] ERROR 2016/06/14 02:41:06 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:41: Minimum brick size limit reached. Out of space. [negroni] Started GET /queue/8d662515743827d44875d9bf146d0f19 [negroni] Completed 200 OK in 73.023µs Should be somewhat similar to logs "Minimum brick size limit reached" instead of "No space" upstream bug: https://github.com/heketi/heketi/issues/380
No, you are viewing this from a GlusterFS point of view. From a "volume" point of view, however it is implemented, there is no space.
If in a cluster we have enough space on each of the node. Then getting "No Space" error is not correct. It failed to create volume because we are giving volume size less than "Minimum volume size/Brick size limit" and that's the error getting logged in the heketi logs. [heketi] ERROR 2016/06/14 02:41:06 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:41: Minimum brick size limit reached. Out of space. [negroni] Started GET /queue/8d662515743827d44875d9bf146d0f19 [negroni] Completed 200 OK in 73.023µs I believe the same error should be displayed to stdout to avoid confusion.
Issue seems to be a duplicate of https://github.com/heketi/heketi/issues/506 and it has been fixed with https://github.com/heketi/heketi/pull/536 .
This is actually imho pretty much the same BZ as https://bugzilla.redhat.com/show_bug.cgi?id=1352778
*** This bug has been marked as a duplicate of bug 1370130 ***