Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

epoch system loom copies should be reflinks when possible #495

Open
barter-simsum opened this issue Jul 20, 2023 · 0 comments
Open

epoch system loom copies should be reflinks when possible #495

barter-simsum opened this issue Jul 20, 2023 · 0 comments

Comments

@barter-simsum
Copy link
Member

a number of filesystems support reflinks which are CoW copies of files that
share common blocks (and initially take up zero space) and only use disk to
store differing blocks.

https://btrfs.readthedocs.io/en/latest/Reflink.html

  • macos apfs
  • linux xfs, btrfs, others

we should use reflinks when the backing filesystem supports it to reduce disk
usage of the epoch system.

@barter-simsum barter-simsum changed the title epoch system pier copies should be reflinks when possible epoch system loom copies should be reflinks when possible Jul 20, 2023
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

No branches or pull requests

1 participant