Understanding a triggered assertion
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
What could possibly lead to errno being set to 7 at the following line:
This is triggered when making a Tio sized copy of many small files on a recent Luster FS.
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 at src/common/mfu_io.c line 1051 and inspect the assertion and surrounding errno handling. Reproduce a Tio-sized copy of many small files on a recent Lustre filesystem, then trace what leads to errno being 7 and document the confirmed cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100