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

[bugzilla at redhat.com]

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

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(nh2-redhatbugzill
                   |                            |a at deditus.de)



--- Comment #2 from Niels de Vos <ndevos at redhat.com> ---
(In reply to nh2 from comment #1)
> I've made a patch that implements this at
> https://github.com/gluster/glusterfs/compare/master...nh2:nanosecond-
> timestamps

Thanks! I had a quick glance over it and it looks ok to me. Could you send this
to our Gerrit instance for review? The workflow to do that is listed here:

 
http://gluster.readthedocs.io/en/latest/Developer-guide/Simplified-Development-Workflow/

Make sure to have a single-line subject, followed by a description of the
problem and solution. Similar to this:

--
posix: use nanosecond accuracy

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
Signed-off-by: Real Name <email>
--

Note that the BUG: tag points to the bug that was cloned for the master branch.
We need patches in the master branch before they get backported to stable
releases.

The Gerrit tools will also insert a Change-Id. This is used by Gerrit to track
updates/modifications to patches. You are not supposed to change the Change-Id
once you posted the change to Gerrit.

Let me know if you hit any problems, or would like an other developer to take
care of this in your name.

Thanks!

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