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

Device priorities for new block allocation on filesystem spanning multiple devices #725

Closed
matthuszagh opened this issue Jan 3, 2024 · 2 comments
Labels
question Not a bug, clarifications, undocumented behaviour

Comments

@matthuszagh
Copy link

This is a question. I apologize if it's been asked before, or if this is the wrong place to ask it, but I wasn't able to find an answer elsewhere. If that's the case, please feel free to direct me elsewhere.

In a multi-device filesystem (data single, metadata dup), how does BTRFS handle on which device to allocate a new data block? I seem to recall reading somewhere that it was the device with the largest free space left. Is that correct? Is there a way to give BTRFS a priority of devices, such that it fills up the highest priority device before the next, etc?

I have a desktop computer with 2 very fast NVMe SSD drives and several very large HDDs. Unfortunately, the BTRFS is filling up the HDDs and ignoring the fast SSDs, greatly affecting the performance. Is there a way to resolve this without removing the HDDs from the filesystem?

@kdave kdave added the question Not a bug, clarifications, undocumented behaviour label Jan 3, 2024
@ErrorNoInternet
Copy link

There is some more discussion at #610, and a patch for preferred-(meta)data: kakra/linux#31

@matthuszagh
Copy link
Author

Thanks! I'll close this, as it's a duplicate issue then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Not a bug, clarifications, undocumented behaviour
Projects
None yet
Development

No branches or pull requests

3 participants