cryptsetup-status8
Report the status for a mapping
Usage
cryptsetup status
[<options>]
<name>
Overview
Reports the status for the mapping <name>.
<options> can be [--header, --disable-locks].
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.
--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.
-
--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).
--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.
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.
Cryptsetup
Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.
Releases
3 releases since Debian 12 (Bookworm); the text changed 2 times.
--batch-mode until Debian 13 (Trixie);
--debug until Debian 13 (Trixie);
--debug-json until Debian 13 (Trixie);
--help until Debian 13 (Trixie);
--version until Debian 13 (Trixie);
-? until Debian 13 (Trixie);
-V until Debian 13 (Trixie);
-q until Debian 13 (Trixie).