[Bugs] [Bug 1230015] [Backup]: Glusterfind pre fails with htime xattr updation error resulting in historical changelogs not available

bugzilla at redhat.com bugzilla at redhat.com
Fri Jun 12 10:38:14 UTC 2015


--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11150 committed in master by Venky Shankar
(vshankar at redhat.com) 
commit e58b55ed9b2e802e6c3e908cbbad71c00f6c5b97
Author: Kotresh HR <khiremat at redhat.com>
Date:   Tue Jun 9 10:44:44 2015 +0530

    features/changelog: Do htime setxattr without XATTR_REPLACE flag

    HTIME_KEY marks the last changelog rolled over. The xattr is
    maintained on .glusterfs/changelog/htime/HTIME.TSTAMP file.
    On every rollover of the changelog file, the xattr is updated.
    It is being updated with XATTR_REPLACE flag as xattr gets
    created during changelog enable. But it is once found that
    the xattrs on the file is cleared and is not reproduced later
    on. This patch protects that case, if it happens by setting
    xattr without XATTR_REPLACE flag in failure case.

    The reason behind doing this in failure case is not to mask
    the actual cause of xattrs getting cleared. This provides
    the log message if the original issue still exists but the
    consequential effects are fixed.

    Also changed the log messages to depict the events happened
    during changelog enable.

    Change-Id: I699ed09a03667fd823d01d65c9c360fa7bc0e455
    BUG: 1230015
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/11150
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>

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

More information about the Bugs mailing list