cryptsetup-status - report the status for a mapping
Contents
Cryptsetup
Part of cryptsetupproject <https://gitlab.com/cryptsetup/cryptsetup/>.
cryptsetup 2.8.0 2025-07-25 CRYPTSETUP-STATUS(8)
Description
Reports the status for the mapping <name>.
<options> can be [--header, --disable-locks].
Name
cryptsetup-status - report the status for a mapping
Options
--batch-mode,-q
Suppresses all confirmation questions. Use with care!
If the --verify-passphrase option is not specified, this option also switches off the passphrase
verification.
--debugor--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.
--disable-locks
Disable lock protection for metadata on disk. This option is valid only for LUKS2 and 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).
--header<deviceorfilestoringtheLUKSheader>
Use a detached (separated) metadata device or file where the LUKS header is stored. This option
allows one to store ciphertext and LUKS header on different devices.
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
Report bugs at cryptsetupmailinglist <cryptsetup@lists.linux.dev> or in Issuesprojectsection
<https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
Please attach output of the failed command with --debug option added.
See Also
CryptsetupFAQ <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
cryptsetup(8), integritysetup(8) and veritysetup(8)
Synopsis
cryptsetupstatus[<options>]<name>
