[Bugs] [Bug 1335285] tar complains: <fileName>: file changed as we read it

[bugzilla at redhat.com]

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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14300 committed in release-3.8 by Niels de
Vos (ndevos at redhat.com) 
------
commit be312da5eac94410c41dac5dc1dde810974a12b7
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Sat Mar 19 11:40:26 2016 +0530

    cluster/afr: Don't let NFS cache stat after writes

    Problem:
    Afr does post-ops after write but the stat buffer it unwinds is at the
    time of write, so if nfs client caches this, it will see different
    ctime when it does stat on it after post-op is done. From NFS client's
    perspective it thinks the file is changed. Tar which depends on this
    to be correct keeps giving 'file changed as we read it' warning.
    If Afr instead has to choose to unwind after post-op, eager-lock,
    delayed-post-op will have to be disabled which will lead to bad
    performance for all write usecases.

    Fix:
    Don't let client cache stat after write.

     >Change-Id: Ic6062acc6e5cdd97a9c83c56bd529ec83cee8a23
     >BUG: 1302948
     >Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
     >Signed-off-by: Anuradha Talur <atalur at redhat.com>
     >Reviewed-on: http://review.gluster.org/13785
     >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: Niels de Vos <ndevos at redhat.com>

    BUG: 1335285
    Change-Id: Ibef4fc80496d12acd15db57713af2e3a1c9109a7
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/14300
    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: Ravishankar N <ravishankar at redhat.com>
    Reviewed-by: Niels de Vos <ndevos 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.