CRYPTSETUP-STATUS(8)

💅 cryptsetup-status — the vibe check for your mappings

okay so bestie, welcome to cryptsetup-status, from the Maintenance Commands section (that's section 8, iykyk) of the cryptsetup manual. it's giving "tell me everything about this mapping, no cap." 🦋

---

✨ NAME ✨

cryptsetup-status — report the status for a mapping 💖

---

🌸 SYNOPSIS 🌸

cryptsetup status [<options>] <name>

---

🎀 DESCRIPTION 🎀

so basically it reports the status for the mapping <name>. that's the whole job. she's a simple girl and she ate. 💅

and just so you know, <options> can be [--header, --disable-locks]. periodt.

---

✨ OPTIONS ✨

• --batch-mode, -q — suppresses all confirmation questions. use with care, bestie, fr fr! 😭 if the --verify-passphrase option is not specified, this option also switches off the passphrase verification.
• --debug or --debug-json — run in debug mode with full diagnostic logs. debug output lines are always prefixed by #. 🐛 if --debug-json is used, additional LUKS2 JSON data structures are printed. (yes, the whole JSON, she's not shy 💜)
• --disable-locks — disable lock protection for metadata on disk. this option is valid only for LUKS2 and is ignored for other formats.

⚠️ WARNING: do not use this option unless you run cryptsetup in a restricted environment where locking is impossible to perform (where /run directory cannot be used). like, for real, don't. 🚨

• --header <device or file storing the LUKS header> — use a detached (separated) metadata device or file where the LUKS header is stored. this option allows one to store the ciphertext and LUKS header on different devices. iconic, honestly. ✨

for commands that change the LUKS header (e.g., luksAddKey), specify the device or file with the LUKS header directly as the LUKS device. 👑

• --help, -? — show help text and default parameters. 🫶
• --usage — show short option help.
• --version, -V — show the program version.

---

🐛 REPORTING BUGS 🐛

found a bug? bestie, report it at the cryptsetup mailing list <cryptsetup@lists.linux.dev> or in the Issues project section <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>. 📬

please attach the output of the failed command with --debug option added. this is not optional, she needs the receipts. 🙈

---

👀 SEE ALSO 👀

• Cryptsetup FAQ <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
• cryptsetup(8), integritysetup(8) and veritysetup(8) 🌈

---

👑 CRYPTSETUP 👑

part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>. ⭐

---

okay that's the whole page, you're welcome. this was cryptsetup 2.8.8, dated 2026-09-07, and yes she's still serving. mwah, go encrypt something responsibly 💖🎀🦋