dsync a file to a symlink to a folder overwrites the symlink
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
I've not tried anything other than dsync, but if I do mpiexec -n 1 dsync single_file ~/tmp/ where ~/tmp/ is a symlink to a different folder, I am finding that dsync overwrites the symlink with the single file instead of treating ~/tmp/ as a directory. This is with v0.12. Symlink is on an NFS filesystem but points to a lustre filesystem if that matters. Compare that to a tool like rsync which seems to check the symlink and confirm its to a directory and then it treats it as a directory.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report with mpiexec -n 1 dsync single_file ~/tmp/, using a symlink to a directory as ~/tmp/, and compare the result with rsync. Start by tracing the dsync command's destination-path handling; done means a symlink to a directory remains intact and the file is placed in the target directory, including for the stated NFS-to-Lustre setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100