Disk expansion using ftruncate on macOS does not pre-allocate disk space
Open
Nobody has claimed this yet.
dima
type: bug
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Environment
(Required) Please provide the output of bin/observer -V. If this test also involves a version change for obproxy, please also provide the output of obproxy -V.
Mapping of the "Target Branch" and "Iteration" properties on the right side:
- Is this a temporary version provided by RD?: No / xxx temporary provision
- Reproducibility: Always Reproducible / Intermittent / Uncertain / Other...
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
The issue names no files, entry points, or tests. Start by reproducing the disk expansion behavior on macOS and trace the database path that uses ftruncate. Done means expansion pre-allocates the expected disk space on macOS and the behavior is covered by a relevant regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- databases, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100