FUTURE POSTS

1. Partial writes, IO_Uring and safety - one day from now
2. Configuration values & Escape hatches - 4 days from now
3. What happens when a sparse file allocation fails? - 6 days from now
4. NTFS has an emergency stash of disk space - 8 days from now
5. Challenge: Giving file system developer ulcer - 11 days from now

And 4 more posts are pending...

There are posts all the way to Feb 17, 2025

RECENT SERIES

1. Challenge (77):
   20 Jan 2025 - What does this code do?
2. Answer (13):
   22 Jan 2025 - What does this code do?
3. Production post-mortem (2):
   17 Jan 2025 - Inspecting ourselves to death
4. Performance discovery (2):
   10 Jan 2025 - IOPS vs. IOPS

RECENT COMMENTS

• Dmitry, Yes, but this is _known_ to be a 64 bits system - since we are allocating 3GB (not possible in 64 bits). Note t...
  By Oren Eini on Answer: What does this code do?
• That's why it is a good idea to compare the return value of `write` to the buffer size. "size_t" can be 32-bit on some system...
  By Dmitry on Answer: What does this code do?
• There's a reason we miss `write_exact` and `read_exact` from the standard library. In fact, I am surprised the chunk is actua...
  By Pyth0n on Challenge: What does this code do?
• kpvleeuwen, I agree, unfortunately I don't have anyone to ask off the top of my head. Thanks, I fixed the headers.
  By Oren Eini on Performance discovery: IOPS vs. IOPS
• It could be interesting to reach out to storage firmware developers and ask what write patterns they think would be useful ex...
  By kpvleeuwen on Performance discovery: IOPS vs. IOPS

Syndication

Main feed
Comments feed