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
AllStoriesComments NewestTopOldest
  1. ▲ 1
    Eatmydata
    story by limbicsystem · 2025-10-14 · 0 comments
  2. 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…
    comment by roryirvine · 2025-06-27 · in Save your disk, write files directly into RAM with /dev/shm
  3. ▲ 2
    libeatmydata – because fsync() should be a no-op
    story by tosh · 2024-09-17 · 0 comments
  4. 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
  5. …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
  6. ▲ 2
    Libeatmydata – because fsync() should be a no-op
    story by eatonphil · 2023-04-03 · 0 comments
  7. …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
  8. ▲ 2
    Libeatmydata – because fsync() should be a no-op
    story by harporoeder · 2021-04-12 · 0 comments
  9. I "recommend" https://github.com/stewartsmith/libeatmydata :)
    comment by FeepingCreature · 2021-02-24 · in M1 Mac owners are experiencing high SSD writes over short periods of time
  10. …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
  11. 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/…
    comment by jwilk · 2017-12-04 · in Using LD_PRELOAD to cheat, inject features and investigate programs (2013)