[Bugs] [Bug 1313311] Dist-geo-rep : geo-rep worker crashed while init with [Errno 34] Numerical result out of range.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1313311



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13560 committed in release-3.7 by Aravinda VK
(avishwan at redhat.com) 
------
commit 5a35bee2057b80809ecdd97abe5cce2d39b2da8a
Author: Aravinda VK <avishwan at redhat.com>
Date:   Tue Dec 29 11:20:39 2015 +0530

    geo-rep: Handle ERANGE error during listxattr

    llistxattr in Geo-rep is two syscall instead of one

    SIZE = llistxattr(PATH, &BUF, 0);
    BUF = create_buf(SIZE);
    _ = llistxattr(PATH, &BUF, SIZE);

    So if any new xattrs added just after first call by any other worker,
    second syscall will fail with ERANGE error.

    Now Geo-rep sends BUF with large size(256*100) and gets value
    with only one syscall. Raises OSError if fails with ERANGE error
    even after sending large BUF.

    Change-Id: I8ade4bbe9a0a8ea908ed9dedcd3f2ff4c6fe6f51
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    BUG: 1313311
    Reviewed-on: http://review.gluster.org/13106
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat at redhat.com>
    (cherry picked from commit 656a0e64e5f465561ed29297421ec150de32f2a1)
    Reviewed-on: http://review.gluster.org/13560

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.