cluster/afr: Fix gfid unsplit code when renamed filename exceeds NAME_MAX

Summary:
- We noticed some folks name their files all the way up to NAME_MAX (usually 255) and when split-brain is encountered, we fail to heal the file.
- This diff puts an upper bound on the number of bytes we will snprintf into the buffer so that we do not fail the rename.
- This is a port of D3646254 to 3.8

Test Plan: Prove test -- can show it fails without patch as well.

Reviewers: #posix_storage, rwareing

Reviewed By: rwareing

Change-Id: I51c6b28374d4a3f21e29044cb727b4b1da7b69e1
Reviewed-on: https://review.gluster.org/18194
Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>

0 files changed, 0 insertions, 0 deletions