dsync: only read valid file extents from sparse files when comparing bytes
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
When dealing with sparse files, dsync --contents and dcmp could each benefit by reading just the valid file extents when comparing byte regions of two files.
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
Start by locating the implementations of dsync --contents and dcmp, then inspect how each reads byte regions when comparing files. The change is done when sparse-file comparisons read only valid file extents while preserving comparison behavior for both commands; the payload names no tests or files to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100