RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1393543 - [RFE] Nanosecond support in rsync
Summary: [RFE] Nanosecond support in rsync
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsync
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Michal Ruprich
QA Contact: Martin Zelený
Adam Kvitek
Depends On: 1432899
Blocks: 1298243 1393869 1473733
TreeView+ depends on / blocked
Reported: 2016-11-09 19:26 UTC by David Kaylor
Modified: 2021-06-10 11:39 UTC (History)
8 users (show)

Fixed In Version: rsync-3.1.2-4.el7
Doc Type: Release Note
Doc Text:
The *rsync* utility now copies files with their original nanosecond part of the time stamp Previously, the *rsync* utility ignored the nanosecond part of the time stamp of files. As a consequence, the nanosecond time stamp of newly created files was always zero. With this update, the *rsync* utility recognizes the nanosecond part. As a result, the newly copied files keep their original nanosecond time stamp on systems that support it.
Clone Of:
Last Closed: 2018-04-10 10:06:32 UTC
Target Upstream Version:

Attachments (Terms of Use)
First (incomplete) patch (18.77 KB, text/plain)
2016-11-16 13:40 UTC, Giuseppe Ragusa
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0692 0 None None None 2018-04-10 10:07:17 UTC

Comment 1 Giuseppe Ragusa 2016-11-16 13:40:08 UTC
Created attachment 1221153 [details]
First (incomplete) patch

To be inserted after all patches already present in RHEL7 rsync spec.

Comment 2 Giuseppe Ragusa 2016-11-16 13:42:09 UTC
Trying to push this RFE forward, I'm testing a backport of upstream commit 839dbff2aaf0277471e1986a3cd0f869e0bdda24 on latest RHEL7 package (3.0.9 based).

I'm attaching my latest test patch which adds further needed parts to the adapted patch from the commit above.

It compiles and runs cleanly (tested as Patch100 on a locally modified src.rpm) but does not actually enable the nanosecond mtime functionality, probably because full advertised support for protocol 31 would be needed.

Is it still considered an acceptable backport for RHEL7 if I go ahead and raise the advertised protocol level?

If it is not, then the only other path forward would be a package rebase (but I would need to check all the additional RHEL patches against latest upstream sources).

Comment 12 Martin Zelený 2017-11-21 15:10:35 UTC
Successfully verified by Case Runs #16374790 (rhel-7) and #16508770 (rhel-alt-7) of TC#560838 - /CoreOS/rsync/Sanity/higher-time-precision

:: [   LOG    ] :: Test if rsync transfer file with same mtime attribute

:: [  BEGIN   ] :: Transfer file :: actually running 'rsync -r -t -vv src/ dst/'
sending incremental file list
delta-transmission disabled for local transfer or --whole-file
total: matches=0  hash_hits=0  false_alarms=0 data=0

sent 107 bytes  received 105 bytes  424.00 bytes/sec
total size is 0  speedup is 0.00
:: [   PASS   ] :: Transfer file (Expected 0, got 0)
:: [   PASS   ] :: File '/var/tmp/rlRun_LOG.eqbZ2zqb' should contain '^testfile$' 
:: [  BEGIN   ] :: Running 'rm  /var/tmp/rlRun_LOG.eqbZ2zqb'
:: [   PASS   ] :: Command 'rm  /var/tmp/rlRun_LOG.eqbZ2zqb' (Expected 0, got 0)
:: [  BEGIN   ] :: Get Modified time of source file :: actually running 'srcMtime=$(stat -c %y src/testfile)'
:: [   PASS   ] :: Get Modified time of source file (Expected 0, got 0)
:: [  BEGIN   ] :: Get Modified time of destination file :: actually running 'dstMtime=$(stat -c %y dst/testfile)'
:: [   PASS   ] :: Get Modified time of destination file (Expected 0, got 0)
:: [   PASS   ] :: mtime of original and transferred files should be the same (Assert: '2017-10-19 00:48:27.357782842 +0200' should equal '2017-10-19 00:48:27.357782842 +0200')
Test-if-rsync-transfer-file-with-same-mtime-attribute result: PASS

Comment 18 errata-xmlrpc 2018-04-10 10:06:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.