[Bugs] [Bug 1333645] NFS+attach tier:IOs hang while attach tier is issued

bugzilla at redhat.com bugzilla at redhat.com
Fri May 6 12:26:29 UTC 2016


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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14236 committed in release-3.7 by Raghavendra
G (rgowdapp at redhat.com) 
------
commit fd8921b9eb03af69815bb2d7cff07b63048c2d5a
Author: Mohammed Rafi KC <rkavunga at redhat.com>
Date:   Tue May 3 14:43:20 2016 +0530

    dht:remember locked subvol and send unlock to the same

    During locking we send lock request to cached subvol,
    and normally we unlock to the cached subvol
    But with parallel fresh lookup on a directory, there
    is a race window where the cached subvol can change
    and the unlock can go into a different subvol from
    which we took lock.

    This will result in a stale lock held on one of the
    subvol.

    So we will store the details of subvol which we took the lock
    and will unlock from the same subvol

    back port of>
    >Change-Id: I47df99491671b10624eb37d1d17e40bacf0b15eb
    >BUG: 1311002
    >Signed-off-by: Mohammed Rafi KC <rkavunga at redhat.com>
    >Reviewed-on: http://review.gluster.org/13492
    >Reviewed-by: N Balachandran <nbalacha at redhat.com>
    >Smoke: Gluster Build System <jenkins at build.gluster.com>
    >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    >Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    >CentOS-regression: Gluster Build System <jenkins at build.gluster.com>

    Change-Id: Ia847e7115d2296ae9811b14a956f3b6bf39bd86d
    BUG: 1333645
    Signed-off-by: Mohammed Rafi KC <rkavunga at redhat.com>
    Reviewed-on: http://review.gluster.org/14236
    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: Raghavendra G <rgowdapp at redhat.com>

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


More information about the Bugs mailing list