mirror of
https://github.com/Llewellynvdm/Tomb.git
synced 2024-11-10 23:20:57 +00:00
added a comment in manpage about resize fail and restore
documentation according to #269
This commit is contained in:
parent
31a78de23f
commit
c8616787f7
12
doc/tomb.1
12
doc/tomb.1
@ -156,11 +156,13 @@ separated list for more than one recipient.
|
|||||||
.B
|
.B
|
||||||
.IP "resize"
|
.IP "resize"
|
||||||
Increase the size of a tomb file to the amount specified by the
|
Increase the size of a tomb file to the amount specified by the
|
||||||
\fI-s\fR option, which is the new size in megabytes (MiB). Full access to the tomb using
|
\fI-s\fR option, which is the new size in megabytes (MiB). Full access
|
||||||
a key (\fI-k\fR) and its password is required. Tombs can only grow and
|
to the tomb using a key (\fI-k\fR) and its password is required. Tombs
|
||||||
can never be made smaller. This command makes use of the cryptsetup(8)
|
can only grow and can never be made smaller. This command makes use of
|
||||||
resize feature and the resize2fs command: its much more practical than
|
the cryptsetup(8) resize feature and the resize2fs command: its much
|
||||||
creating a new tomb and moving everything into it.
|
more practical than creating a new tomb and moving everything into
|
||||||
|
it. There is no data-loss if a failure occurs during resize: the
|
||||||
|
command can be re-launched and the resize operation will complete.
|
||||||
|
|
||||||
.B
|
.B
|
||||||
.IP "engrave"
|
.IP "engrave"
|
||||||
|
Loading…
Reference in New Issue
Block a user