[Bugs] [Bug 1230007] [Backup]: 'New' as well as 'Modify' entry getting recorded for a newly created hardlink

[bugzilla at redhat.com]

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



--- Comment #5 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11137 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
------
commit a6c53571a9a7c74d0fa2683b4ba04682bd6a46ad
Author: Saravanakumar Arumugam <sarumuga at redhat.com>
Date:   Tue Jun 9 17:49:58 2015 +0530

    features/changelog: Avoid setattr fop logging during rename

    Problem:
            When a file is renamed and the (renamed)file's Hashing
    falls into a different brick, DHT creates a special file(linkto file)
    in the brick(Hashed subvolume) and carries out setattr operation
    on that file.

    Currently, Changelog records this(setattr) operation in Hashed
    subvolume. glusterfind in turn records this operation
    as MODIFY operation.

    So, there is a NEW entry in Cached subvolume and MODIFY entry
    in Hashed subvolume for the same file.

    Solution:
            Avoid logging setattr operation carried out, by
    marking the operation as internal fop using xdata.

    In changelog translator, check whether setattr is set
    as internal fop and skip accordingly.

    Change-Id: I21b09afb5a638b88a4ccb822442216680b7b74fd
    BUG: 1230007
    Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Reviewed-on: http://review.gluster.org/11137
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    Tested-by: Raghavendra G <rgowdapp at redhat.com>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.