REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative path name instead of absolute pathname) posted (#1) for review on master by Atin Mukherjee (amukherj)
Please note with the current design of volfile it can not be guaranteed that volname and brickpath can have upto _POSIX_PATH_MAX characters. The validation goes like : strlen(volname) + strlen(brickpath) + strlen(hostname/ip) <= _POSIX_PATH_MAX.
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative path name instead of absolute pathname) posted (#2) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative path name instead of absolute pathname) posted (#3) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative path name instead of absolute pathname) posted (#4) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative path name instead of absolute pathname) posted (#5) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative path name instead of absolute pathname) posted (#6) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative path name instead of absolute pathname) posted (#7) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative pathname instead of absolute pathname) posted (#8) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Length check for volume name and brick path is done on relative pathname instead of absolute pathname) posted (#9) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Volname, brickpath & volfpath length validation) posted (#10) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/7420 (glusterd : Volname, brickpath & volfpath length validation) posted (#11) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/7420 committed in master by Vijay Bellur (vbellur) ------ commit e73fc9939aecfa9f7955653d02f12243aba02fc6 Author: Atin Mukherjee <amukherj> Date: Tue Apr 8 17:10:25 2014 +0530 glusterd : Volname, brickpath & volfpath length validation While creating a volume and adding a brick validation for _POSIX_PATH_MAX is done on absolute pathname instead of relative pathname due to which a brickpath having less than _POSIX_PATH_MAX may also fail the validation if the directory length is greater than (_POSIX_PATH_MAX -strlen(brickpath/volume name). Also this fix addresses one cli response message correction which says the volume file is too long instead of brick path is too long (when brickpath length validation doesn't fail and vol file length validation fails.) It is also important to note that with the current design of volfile naming, it can not be guranteed that volname and brickpath can have max of _POSIX_PATH_MAX characters. Change-Id: I1283d1f9dea96ae797620002c8723719f26a866d BUG: 1085330 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/7420 Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
*** Bug 840349 has been marked as a duplicate of this bug. ***
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