[Bugs] [Bug 1422074] GlusterFS truncates nanoseconds to microseconds when setting mtime

[bugzilla at redhat.com]

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



--- Comment #11 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16667 committed in master by Jeff Darcy
(jdarcy at redhat.com) 
------
commit ce8d8195dc253a87cceaaeeb1a725090471ae4f8
Author: Niklas Hambüchen <mail at nh2.me>
Date:   Sat Feb 18 00:49:02 2017 +0100

    posix: use nanosecond accuracy when available

    Programs that set mtime, such as `rsync -a`, don't work correctly on
    GlusterFS, because it sets the nanoseconds to 000. This creates
    problems for incremental backups, where files get accidentally copied
    again and again.

    For example, consider `myfile` on an ext4 system, being copied to a
    GlusterFS volume, with `rsync -a` and then `cp -u` in turn. You'd
    expect that after the first `rsync -a`, `cp -u` agrees that the file
    need not be copied.

    BUG: 1422074
    Change-Id: I89c7b6a73e2e06c02851ff76b7e5cdfaa271e985
    Signed-off-by: Niklas Hambüchen <mail at nh2.me>
    Reviewed-on: https://review.gluster.org/16667
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>
    Tested-by: Jeff Darcy <jdarcy at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy 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.