Design: Should laminating a file sync its extents?
Open
Nobody has claimed this yet.
question
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Currently, UnifyFS requires you to fsync() your extents before laminating the file:
```
fp = fopen("checkpoint1.chk")
write(fp, )
…
fsync(fp)
fclose(fp)
chmod("checkpoint1.chk", 0444) /* laminate */
```
Should a laminate implicitly fsync the extents as well? My gut feeling would be yes. Thoughts?
Contributor guide
No contributing guide indexed for this repository
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 source file or test. Start by tracing the chmod-based lamination path and the existing fsync handling; done requires an agreed answer about whether lamination synchronizes extents, with the intended behavior and validation defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100