despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op

Preview meta tags from the despairlabs.com website.

Linked Hostnames

6

Thumbnail

Search Engine Appearance

Google

https://despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op

fsync() after open() is an elaborate no-op

I have spent the last couple of years of my life trying to make sense of fsync() and bringing OpenZFS up to code. I’ve read a lot of horror stories about this apparently-simple syscall in that time, usually written by people who tried very hard to get it right but ended up losing data in different ways. I hesitate to say I enjoy reading these things, because they usually start with some catastrophic data loss situation and that’s just miserably unfair. At least, I think they’re important reads, and I’m always glad to see another story of fsync() done right, or done wrong.



Bing

fsync() after open() is an elaborate no-op

https://despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op

I have spent the last couple of years of my life trying to make sense of fsync() and bringing OpenZFS up to code. I’ve read a lot of horror stories about this apparently-simple syscall in that time, usually written by people who tried very hard to get it right but ended up losing data in different ways. I hesitate to say I enjoy reading these things, because they usually start with some catastrophic data loss situation and that’s just miserably unfair. At least, I think they’re important reads, and I’m always glad to see another story of fsync() done right, or done wrong.



DuckDuckGo

https://despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op

fsync() after open() is an elaborate no-op

I have spent the last couple of years of my life trying to make sense of fsync() and bringing OpenZFS up to code. I’ve read a lot of horror stories about this apparently-simple syscall in that time, usually written by people who tried very hard to get it right but ended up losing data in different ways. I hesitate to say I enjoy reading these things, because they usually start with some catastrophic data loss situation and that’s just miserably unfair. At least, I think they’re important reads, and I’m always glad to see another story of fsync() done right, or done wrong.

  • General Meta Tags

    7
    • title
      fsync() after open() is an elaborate no-op · blog · despair labs
    • charset
      utf-8
    • viewport
      width=device-width, initial-scale=1
    • article:section
      blog
    • article:published_time
      2025-03-13T00:00:00+11:00
  • Open Graph Meta Tags

    7
    • og:url
      https://despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op/
    • og:site_name
      despair labs
    • og:title
      fsync() after open() is an elaborate no-op
    • og:description
      I have spent the last couple of years of my life trying to make sense of fsync() and bringing OpenZFS up to code. I’ve read a lot of horror stories about this apparently-simple syscall in that time, usually written by people who tried very hard to get it right but ended up losing data in different ways. I hesitate to say I enjoy reading these things, because they usually start with some catastrophic data loss situation and that’s just miserably unfair. At least, I think they’re important reads, and I’m always glad to see another story of fsync() done right, or done wrong.
    • US country flagog:locale
      en_us
  • Twitter Meta Tags

    4
    • twitter:card
      summary_large_image
    • twitter:image
      https://despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op/thumbnail.jpg
    • twitter:title
      fsync() after open() is an elaborate no-op
    • twitter:description
      I have spent the last couple of years of my life trying to make sense of fsync() and bringing OpenZFS up to code. I’ve read a lot of horror stories about this apparently-simple syscall in that time, usually written by people who tried very hard to get it right but ended up losing data in different ways. I hesitate to say I enjoy reading these things, because they usually start with some catastrophic data loss situation and that’s just miserably unfair. At least, I think they’re important reads, and I’m always glad to see another story of fsync() done right, or done wrong.
  • Link Tags

    6
    • me
      https://social.lol/@robn
    • me
      https://robn.au/
    • stylesheet
      /css/site.css
    • stylesheet
      /css/fontawesome.min.css
    • stylesheet
      /css/brands.min.css

Links

18