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

Space re-balancing with large file blocks #3540

Closed
don-brady opened this issue Jun 29, 2015 · 2 comments
Closed

Space re-balancing with large file blocks #3540

don-brady opened this issue Jun 29, 2015 · 2 comments
Labels
Status: Design Review Needed Architecture or design is under discussion Status: Inactive Not being actively updated Status: Stale No recent activity for issue

Comments

@don-brady
Copy link
Contributor

Commit f1512ee (illumos issue 5027) introduced support for larger blocks in ZFS (> 128K).
 
VDEV Space Re-balancing
 
The traditional VDEV space re-balancing occurred by means of a bias based on a 512K metaslab_aliquot and the number of VDEV children.  This bias mechanism will not function correctly with large allocation sizes. An alternate method may need to be devised to allow effective re-balancing when streams of large allocations occur.

Intel is currently working on a alternate re-balancing solution for large blocks.

@behlendorf
Copy link
Contributor

This recently came up in the context of #3389. The only significant concern was this this could potentially lead to a slight imbalance in the free space. Although the expectation was that in practice this imbalance would be corrected for over time due to the bias.

One possible solution to this would be to scale the metaslab_aliquot size based on the dataset's maximum recordsize. Setting it as 4 * recordsize would produce similar behavior but it might not be convenient to access the dataset size while allocating. Better ideas welcome!

@stale
Copy link

stale bot commented Aug 25, 2020

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale No recent activity for issue label Aug 25, 2020
@stale stale bot closed this as completed Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Design Review Needed Architecture or design is under discussion Status: Inactive Not being actively updated Status: Stale No recent activity for issue
Projects
None yet
Development

No branches or pull requests

3 participants
@behlendorf @don-brady and others