NDCTL-CHECK-NAMESPACE(1)

💖 ndctl-check-namespace(1) 💖

okay bestie so this is a page from the ndctl manual, and it's literally all about ndctl-check-namespace — the little icon that checks whether your namespace metadata is giving consistent or messy. let's get into it 🫶

---

✨ NAME ✨

ndctl-check-namespace — check namespace metadata consistency 💅

---

🌸 SYNOPSIS 🌸

ndctl check-namespace <namespace> [<options>]

---

🦋 DESCRIPTION 🦋

so, a namespace that's chillin' in sector mode has metadata sitting on it that describes the kernel BTT (Block Translation Table). and like, that metadata can get weird. the check-namespace command is here to check the consistency of that metadata, and if it's got enough info to work with, it can optionally also try to repair it. bestie behaviour fr fr 💖

okay important thing: the namespace you're checking has to be disabled before you start a check on it, just as a precautionary measure. but the --force option can override that, if you're feeling spicy 🌶️

---

🎀 EXAMPLES 🎀

Check a namespace (only report errors) — like, no touchy, just looking 👀

ndctl disable-namespace namespace0.0
ndctl check-namespace namespace0.0

Check a namespace, and perform repairs if possible — now we're fixing things, main character energy ✨

ndctl disable-namespace namespace0.0
ndctl check-namespace --repair namespace0.0

---

👑 OPTIONS 👑

• -R, --repair — perform metadata repairs if possible. if you don't pass this, the raw namespace contents will not be touched at all. hands off, respectfully 🙈
• -L, --rewrite-log — regenerate the BTT log and write it to media. this one's for converting from the old (pre 4.15) padding format that was incompatible with other BTT implementations over to the updated format. heads up though: this requires the --repair option to be provided too.

⚠️ WARNING: Do not interrupt this operation as it can potentially cause unrecoverable metadata corruption. It is highly recommended to create a backup of the raw namespace before attempting this.

no like seriously, do NOT interrupt it. back up your raw namespace first, i'm begging 😭

• -f, --force — unless you specify this, a check-namespace operation will fail if the namespace is presently active. specifying --force causes the namespace to be disabled before checking. it's giving "fine, i'll do it myself" 💅
• -v, --verbose — emit debug messages for the namespace check process. yapping mode: enabled 🗣️
• -r, --region= — a regionX device name, or a region id number. restrict the operation to the specified region(s). the keyword all can be specified to indicate the lack of any restriction — however, this is the same as not supplying a --region option at all. so like, all and nothing are the same vibe, iykyk 🌈
• -b, --bus= — a bus id number, or a provider string (e.g. "ACPI.NFIT"). restrict the operation to the specified bus(es). the keyword all can be specified to indicate the lack of any restriction — however, this is the same as not supplying a --bus option at all. same energy as above, no cap 🧚

---

💜 COPYRIGHT 💜

Copyright © 2016 - 2022, Intel Corporation. License GPLv2: GNU GPL version 2 http://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

---

⭐ SEE ALSO ⭐

• ndctl-disable-namespace(1)
• ndctl-enable-namespace(1)
• UEFI NVDIMM Label Protocol <http://www.uefi.org/sites/default/files/resources/UEFI_Spec_2_7.pdf>

---

and that's the whole page, bestie, we ate and left no crumbs 🍓 this was the ndctl manual, page dated 2026-07-07 — go check those namespaces, but disable them first, mwah 💋✨