[Bugs] [Bug 1334441] SAMBA-VSS : Permission denied issue while restoring the directory from windows client 1 when files are deleted from windows client 2

bugzilla at redhat.com bugzilla at redhat.com
Fri May 13 05:52:50 UTC 2016


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



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14290 committed in release-3.7 by Raghavendra
Talur (rtalur at redhat.com) 
------
commit ff7f6fc82cfe3a6af4bf3f339c31843a0e9c9b28
Author: Raghavendra Talur <rtalur at redhat.com>
Date:   Mon May 9 21:06:07 2016 +0530

    gfapi: clear loc.gfid when retrying after ESTALE

    If an ESTALE is returned as result of a revalidate lookup, it means the
    previous gfid and inode are to be discarded and lookup has to be tried
    as a fresh one. A fresh lookup should not have loc.gfid set. We were
    creating a new inode and passing it down but not clearing loc.gfid.
    This patch fixes that.

    >Change-Id: Ib192ada0528b5fb5e49b4e2555f2bcab62710e2d
    >BUG: 1334444
    >Signed-off-by: Raghavendra Talur <rtalur at redhat.com>
    >Reviewed-on: http://review.gluster.org/14274
    >Smoke: Gluster Build System <jenkins at build.gluster.com>
    >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    >Reviewed-by: Niels de Vos <ndevos at redhat.com>
    >CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    >(cherry picked from commit b2f09e531029f573772a09572cee0f8e1855481b)

    Change-Id: Ib192ada0528b5fb5e49b4e2555f2bcab62710e2d
    BUG: 1334441
    Signed-off-by: Raghavendra Talur <rtalur at redhat.com>
    Reviewed-on: http://review.gluster.org/14290
    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: Rajesh Joseph <rjoseph at redhat.com>

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


More information about the Bugs mailing list