Skip to content

docs: warn FIEMAP locations are unstable#693

Closed
Komzpa wants to merge 1 commit into
koverstreet:masterfrom
Komzpa:komzpa/fiemap-stability-docs
Closed

docs: warn FIEMAP locations are unstable#693
Komzpa wants to merge 1 commit into
koverstreet:masterfrom
Komzpa:komzpa/fiemap-stability-docs

Conversation

@Komzpa

@Komzpa Komzpa commented Jun 28, 2026

Copy link
Copy Markdown

Summary

Document that FIEMAP/filefrag extent locations on bcachefs are observations, not a stable userspace write ABI.

This addresses the safety question from koverstreet/bcachefs#774: even with a preallocated file or nocow, userspace should not write directly to the reported block device offsets while the filesystem is mounted, because bcachefs may move extents in the background and userspace cannot lock those moves out.

The supported direction for swapfile-style block I/O is filesystem-coordinated handling, not a manually constructed device-mapper table. The active swapfile work is #646, related to koverstreet/bcachefs#368.

Testing

  • git diff --check
  • python3 -m py_compile doc/macro2rst.py
  • rst2man --halt=2 doc/bcachefs.5.rst.tmpl /tmp/bcachefs.5.rst.tmpl.man

Related

@koverstreet

Copy link
Copy Markdown
Owner

Merged — cherry-picked onto master, authorship preserved. Thanks!

@koverstreet koverstreet closed this Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants