You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This probably affects other types/modes of copying, too, since we have a lot of shurt-cutting currently.
Steps to reproduce:
Have two files that are hardlinks
Copy them with -dv to some other directory
Expected behavior: Both files are copied, the resulting two files are hardlinks of each other but not of the original files, and both copy operations are reported.
Actual behavior: Both files are copied, the resulting two files are hardlinks of each other but not of the original files, but only one copy operation is reported.
This probably affects other types/modes of copying, too, since we have a lot of shurt-cutting currently.
Steps to reproduce:
-dv
to some other directoryExpected behavior: Both files are copied, the resulting two files are hardlinks of each other but not of the original files, and both copy operations are reported.
Actual behavior: Both files are copied, the resulting two files are hardlinks of each other but not of the original files, but only one copy operation is reported.
Demonstrator:
(In this example, the copied files "randomly" got the same inode ID twice in a row, but they might have gotten a different ID in the second run.)
Found while reviewing #6208
The text was updated successfully, but these errors were encountered: