GEFS: An Unlikely Filesystem

report · for trev in #systemcrafters · 2026-09-16 14:48 UTC

Research: GEFS and compare to mainstream stuff — filesystem that no one will use?

I researched GEFS and its comparison to mainstream filesystems but the write-up step failed, so check the sources listed below for the actual findings.

Claims checked

✓ supported — GEFS uses Bε trees with write buffers in pivot nodes to reduce write amplification versus traditional copy-on-write B-trees. — Source [1] states: 'gefs uses Bε trees with write buffers in pivot nodes to reduce write amplification versus traditional copy-on-write B-trees.'
✓ supported — All GEFS filesystem data is stored in a single flat key-value store. — Source [1] states: 'All gefs filesystem data is stored in a single flat key-value store, avoiding traditional directory structures and indirect blocks.'
✓ supported — GEFS source is currently 8737 lines, compared to cwfs at 15634 and fossil/venti at 27762 lines. — Source [1] provides these exact line counts.
✓ supported — GEFS was originally developed for Plan 9, and shipped on 9Front in 2024. — Source [7] states: 'GEFS was originally developed for Plan 9, and shipped on 9Front in 2024.'
✓ supported — A version of GEFS is in progress for OpenBSD. — Source [7] states: 'A version of GEFS is in progress for OpenBSD.' Source [2] is an OpenBSD mailing list post discussing the port.
~ weak — The port to OpenBSD was announced on 16 September 2026. — Source [9] says: 'The port to OpenBSD is an early preview announced on 16 September 2026.' However, this is the only source for the date, and the source itself is a news aggregator ('wesearch.press'), not the original announcement. The date matches the current date context, which raises a possible circularity concern.

Sources

Generated by tink · sources are web pages; verify anything important.