Update raw send documentation
This patch simply clarifies some of the limitations related to raw sends in the man page. No functional changes. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Jason Cohen <jwittlincohen@gmail.com> Signed-off-by: Tom Caputi <tcaputi@datto.com> Closes #8503 Closes #8544
This commit is contained in:
parent
1b939560be
commit
dd29864b01
|
@ -3500,7 +3500,11 @@ set when the stream is received.
|
||||||
If the
|
If the
|
||||||
.Fl F
|
.Fl F
|
||||||
flag is specified when this stream is received, snapshots and file systems that
|
flag is specified when this stream is received, snapshots and file systems that
|
||||||
do not exist on the sending side are destroyed.
|
do not exist on the sending side are destroyed. If the
|
||||||
|
.Fl R
|
||||||
|
flag is used to send encrypted datasets, then
|
||||||
|
.Fl w
|
||||||
|
must also be specified.
|
||||||
.It Fl e, -embed
|
.It Fl e, -embed
|
||||||
Generate a more compact stream by using
|
Generate a more compact stream by using
|
||||||
.Sy WRITE_EMBEDDED
|
.Sy WRITE_EMBEDDED
|
||||||
|
@ -3843,7 +3847,13 @@ recompressed by the receive process. Unencrypted streams can be received as
|
||||||
encrypted datasets, either through inheritance or by specifying encryption
|
encrypted datasets, either through inheritance or by specifying encryption
|
||||||
parameters with the
|
parameters with the
|
||||||
.Fl o
|
.Fl o
|
||||||
options.
|
options. Note that the
|
||||||
|
.Sy keylocation
|
||||||
|
property cannot be overridden to
|
||||||
|
.Sy prompt
|
||||||
|
during a receive. This is because the receive process itself is already using
|
||||||
|
stdin for the send stream. Instead, the property can be overridden after the
|
||||||
|
receive completes.
|
||||||
.Pp
|
.Pp
|
||||||
The added security provided by raw sends adds some restrictions to the send
|
The added security provided by raw sends adds some restrictions to the send
|
||||||
and receive process. ZFS will not allow a mix of raw receives and non-raw
|
and receive process. ZFS will not allow a mix of raw receives and non-raw
|
||||||
|
|
Loading…
Reference in New Issue