A clear explanation of metaslab groups and gangs, in ZFS?
I'm trying to troubleshoot a problem related to metaslab and spacemaps in ZFS on FreeBSD, for which I'd like to have a clear understanding of how these work. Most of the docs make sense. But I keep coming across gangs, and groups, and the explanations for these terms are very hazy and vague. It makes it hard to be sure I know what happens.
To use as a concrete example, suppose I create a pool with two striped 8TB HDDs (non-redundant storage, one vdev= one HDD to keep the example simple), and put a pool and dataset on it. I understand ZFS will initially carve the free capacity up into "about" 200 metaslabs per vdev (about 400 metaslabs total, 30 ~ 40GB each), but after that the picture gets unclear.
As time goes on, and files of varying sizes are added and deleted, how does free space/metaslab management broadly evolve, and where do metaslab groups and "gangs" (whatever these are) come into the picture?
I'm mostly after a "broad/big-ish picture", to orient me and contextualise the terms I don't understand, and see how these all fit together at a quite high level.
Thanks.
zfs
asked Jan 5 at 23:56
StilezStilez
76311021
add a comment |
I'm trying to troubleshoot a problem related to metaslab and spacemaps in ZFS on FreeBSD, for which I'd like to have a clear understanding of how these work. Most of the docs make sense. But I keep coming across gangs, and groups, and the explanations for these terms are very hazy and vague. It makes it hard to be sure I know what happens.
To use as a concrete example, suppose I create a pool with two striped 8TB HDDs (non-redundant storage, one vdev= one HDD to keep the example simple), and put a pool and dataset on it. I understand ZFS will initially carve the free capacity up into "about" 200 metaslabs per vdev (about 400 metaslabs total, 30 ~ 40GB each), but after that the picture gets unclear.
As time goes on, and files of varying sizes are added and deleted, how does free space/metaslab management broadly evolve, and where do metaslab groups and "gangs" (whatever these are) come into the picture?
I'm mostly after a "broad/big-ish picture", to orient me and contextualise the terms I don't understand, and see how these all fit together at a quite high level.
Thanks.
zfs
asked Jan 5 at 23:56
StilezStilez
76311021
add a comment |
I'm trying to troubleshoot a problem related to metaslab and spacemaps in ZFS on FreeBSD, for which I'd like to have a clear understanding of how these work. Most of the docs make sense. But I keep coming across gangs, and groups, and the explanations for these terms are very hazy and vague. It makes it hard to be sure I know what happens.
To use as a concrete example, suppose I create a pool with two striped 8TB HDDs (non-redundant storage, one vdev= one HDD to keep the example simple), and put a pool and dataset on it. I understand ZFS will initially carve the free capacity up into "about" 200 metaslabs per vdev (about 400 metaslabs total, 30 ~ 40GB each), but after that the picture gets unclear.
As time goes on, and files of varying sizes are added and deleted, how does free space/metaslab management broadly evolve, and where do metaslab groups and "gangs" (whatever these are) come into the picture?
I'm mostly after a "broad/big-ish picture", to orient me and contextualise the terms I don't understand, and see how these all fit together at a quite high level.
Thanks.
zfs
asked Jan 5 at 23:56
StilezStilez
76311021
I'm trying to troubleshoot a problem related to metaslab and spacemaps in ZFS on FreeBSD, for which I'd like to have a clear understanding of how these work. Most of the docs make sense. But I keep coming across gangs, and groups, and the explanations for these terms are very hazy and vague. It makes it hard to be sure I know what happens.
To use as a concrete example, suppose I create a pool with two striped 8TB HDDs (non-redundant storage, one vdev= one HDD to keep the example simple), and put a pool and dataset on it. I understand ZFS will initially carve the free capacity up into "about" 200 metaslabs per vdev (about 400 metaslabs total, 30 ~ 40GB each), but after that the picture gets unclear.
As time goes on, and files of varying sizes are added and deleted, how does free space/metaslab management broadly evolve, and where do metaslab groups and "gangs" (whatever these are) come into the picture?
I'm mostly after a "broad/big-ish picture", to orient me and contextualise the terms I don't understand, and see how these all fit together at a quite high level.
Thanks.
zfs
zfs
asked Jan 5 at 23:56
StilezStilez
76311021
asked Jan 5 at 23:56
StilezStilez
76311021
edited Jan 6 at 0:02
Stilez
asked Jan 5 at 23:56
StilezStilez
76311021
asked Jan 5 at 23:56
StilezStilez
76311021
asked Jan 5 at 23:56
StilezStilez
76311021
76311021
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1391027%2fa-clear-explanation-of-metaslab-groups-and-gangs-in-zfs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1391027%2fa-clear-explanation-of-metaslab-groups-and-gangs-in-zfs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
