Red Hat Bugzilla – Bug 829916
Avoid a dry-run error trying to stat a prior hardlink
Last modified: 2016-08-16 09:46:37 EDT
Description of problem:
When you run rsync with --dry-run and -H parameters, and there are hardlinks on the server side, it tries to stat the hardlink that doesn't exist yet.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.A server with hardlinks
2.rsync -H --dry-run
Errors like this:
rsync: stat "/path/file" failed: No such file or directory (2)
This bug was fixed on rsync 3.0.7, at the following commit:
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
How is it possible to reproduce the bug?
I have tried these commands:
mkdir s/ t/
ln s/lala s/hard
rsync --rsh=ssh -avz -H --dry-run s/ localhost:/tmp/t/
I have also tried with more hardlinks pointing to the same file and transferring in the opposite direction (from the server) and with none/some/all of the files present in the target directory.
The output usually looks like this:
$ rsync --rsh=ssh -avH --dry-run s/ localhost:/tmp/t/
sending incremental file list
hard => lala
sent 70 bytes received 30 bytes 200.00 bytes/sec
total size is 0 speedup is 0.00 (DRY RUN)
My version is (I guess the architecture is not important here):
I use the same machine as a server and as a client, but connecting through ssh.
I have tried the commands and some of the mentioned scenarios from the comment #3 on the same architecture as the reporter has, but without any success (no errors).
This request was evaluated by Red Hat Engineering for inclusion in a Red
Hat Enterprise Linux maintenance release.
As this bug has been in NEEDINFO for an extended period of time we are going
to close this bug due to inactivity. If you would like to pursue this
matter feel free to reopen this bug and attach the needed information.
With the goal of minimizing risk of change for deployed systems, and in
response to customer and partner requirements, Red Hat takes a conservative
approach when evaluating enhancements for inclusion in maintenance updates
for currently deployed products. The primary objectives of update releases
are to enable new hardware platform support and to resolve critical
However, Red Hat will further review this request for potential inclusion
in future major releases of Red Hat Enterprise Linux.