eessppeelllloo/cryptsetup
1
0
Fork 0
mirror of https://gitlab.com/cryptsetup/cryptsetup.git synced 2025-12-12 03:10:08 +01:00
Code Issues Packages Projects Releases Wiki Activity

Better explain --persistent option for flag removals.

Browse Source 
Also fix a error message that was not displayed
properly for the persistent discard flag incompatibility.

Fixes: #558.
This commit is contained in:
Milan Broz
2020-05-02 17:08:19 +02:00
parent 533b874590
commit e759ebe0bd
2 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
man/cryptsetup.8
View File

@@ -1306,10 +1306,15 @@ performance on most of the modern storage devices and also with some
hw encryption accelerators.
.TP
.B "\-\-persistent"
If used with LUKS2 devices and activation commands like \fIopen\fR,
If used with LUKS2 devices and activation commands like \fIopen\fR or \fIrefresh\fR,
the specified activation flags are persistently written into metadata
and used next time automatically even for normal activation.
(No need to use cryptab or other system configuration files.)
If you need to remove a persistent flag, use \fI\-\-persistent\fR without
the flag you want to remove (e.g. to disable persistently stored discard flag,
use \fI\-\-persistent\fR without \fI\-\-allow-discards\fR).
Only \fI\-\-allow-discards\fR, \fI\-\-perf\-same_cpu_crypt\fR,
\fI\-\-perf\-submit_from_crypt_cpus\fR and \fI\-\-integrity\-no\-journal\fR
can be stored persistently.