1CRYPTSETUP-STATUS(8)         Maintenance Commands         CRYPTSETUP-STATUS(8)
2
3
4

NAME

6       cryptsetup-status - report the status for a mapping
7

SYNOPSIS

9       cryptsetup status [<options>] <name>
10

DESCRIPTION

12       Reports the status for the mapping <name>.
13
14       <options> can be [--header, --disable-locks].
15

OPTIONS

17       --header <device or file storing the LUKS header>
18           Use a detached (separated) metadata device or file where the LUKS
19           header is stored. This option allows one to store ciphertext and
20           LUKS header on different devices.
21
22           For commands that change the LUKS header (e.g. luksAddKey), specify
23           the device or file with the LUKS header directly as the LUKS
24           device.
25
26       --disable-locks
27           Disable lock protection for metadata on disk. This option is valid
28           only for LUKS2 and ignored for other formats.
29
30           WARNING: Do not use this option unless you run cryptsetup in a
31           restricted environment where locking is impossible to perform
32           (where /run directory cannot be used).
33
34       --batch-mode, -q
35           Suppresses all confirmation questions. Use with care!
36
37           If the --verify-passphrase option is not specified, this option
38           also switches off the passphrase verification.
39
40       --debug or --debug-json
41           Run in debug mode with full diagnostic logs. Debug output lines are
42           always prefixed by #.
43
44           If --debug-json is used, additional LUKS2 JSON data structures are
45           printed.
46
47       --version, -V
48           Show the program version.
49
50       --usage
51           Show short option help.
52
53       --help, -?
54           Show help text and default parameters.
55

REPORTING BUGS

57       Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or
58       in Issues project section
59       <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
60
61       Please attach output of the failed command with --debug option added.
62

SEE ALSO

64       Cryptsetup FAQ
65       <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
66
67       cryptsetup(8), integritysetup(8) and veritysetup(8)
68

CRYPTSETUP

70       Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.
71
72
73
74cryptsetup 2.5.0                  2022-07-28              CRYPTSETUP-STATUS(8)
Impressum