Hacker GitHub

← All repos

stewartsmith/libeatmydata

View on GitHub ↗ ★ 500 C

libeatmydata - because fsync() should be a no-op

11 mentions on Hacker News by 11 people: 4 stories, 7 comments · first 2017-12-04 · latest 2025-10-14

Mentions per year 11 mentions · busiest year 2023 (4)
20082026
  1. Have a look at libeatmydata - https://github.com/stewartsmith/libeatmydata Things will still get written to disk eventually, it's just that fsync() returns instantly without actually doing anything. It's sometimes used in CI and…
  2. You can also add journal_async_commit,noauto_da_alloc > maybe disable flushes with https://github.com/stewartsmith/libeatmydata overlayfs has a volatile mount option that has that effect. So stacking a volatile overlayfs with the upper and…
    comment by the8472 · 2023-05-11 · in Bcachefs – A New COW Filesystem
  3. …data=writeback, barrier=0, bump up dirty_ratio, tune ^has_journal, maybe disable flushes with https://github.com/stewartsmith/libeatmydata
    comment by viraptor · 2023-05-11 · in Bcachefs – A New COW Filesystem
  4. …using that, you'd probably be comfortable disabling fsync on the datasets for those apps. [0]: https://github.com/stewartsmith/libeatmydata
    comment by hardwaresofton · 2023-04-03 · in The secret life of fsync
  5. I "recommend" https://github.com/stewartsmith/libeatmydata :)
  6. …for the toolbox, to be used very carefully, after thinking about the consequences: libeatmydata: https://github.com/stewartsmith/libeatmydata It disables fsync, o_sync etc, making them no-ops, essentially making the programs writes unsafe.…
    comment by Twirrim · 2019-02-18 · in LD_PRELOAD: The Hero We Need and Deserve
  7. Interesting projects that employ LD_PRELOAD: https://github.com/stewartsmith/libeatmydata https://github.com/wolfcw/libfaketime https://cwrap.org/ https://github.com/dex4er/fakechroot https://blitiri.com.ar/p/libfiu/…