1NVME-COPY(1)                      NVMe Manual                     NVME-COPY(1)
2
3
4

NAME

6       nvme-copy - Send an NVMe Simple Copy command, provide results
7

SYNOPSIS

9       nvme-copy <device> [--sdlba=<sdlba> | -d <sdlba>]
10                               [--blocks=<nlb-list,> | -b <nlb-list,>]
11                               [--slbs=<slbas,> | -s <slbas,>]
12                               [--limited-retry | -l]
13                               [--force-unit-access | -f]
14                               [--prinfow=<prinfow> | -p <prinfow>]
15                               [--prinfor=<prinfor> | -P <prinfor>]
16                               [--ref-tag=<reftag> | -r <reftag>]
17                               [--expected-ref-tags=<reftag,> | -R <reftag,>]
18                               [--app-tag=<apptag> | -a <apptag>]
19                               [--expected-app-tags=<apptag,> | -A <apptag,>]
20                               [--app-mask=<appmask> | -m <appmask>]
21                               [--expected-app-masks=<appmask,> | -M <appmask,>]
22                               [--dir-type=<type> | -T <type>]
23                               [--dir-spec=<spec> | -S <spec>]
24                               [--format=<entry-format> | -F <entry-format>]
25

DESCRIPTION

27       The Copy command is used by the host to copy data from one or more
28       source logical block ranges to a single consecutive destination logical
29       block range.
30

OPTIONS

32       --sdlba=<sdlba>, -d <sdlba>
33           64-bit addr of first destination logical block
34
35       --blocks=<nlb-list,>, -b <nlb-list,>
36           Comma separated list of the number of blocks in each range
37
38       --slbs=<slbas,>, -s <slbas,>
39           Comma separated list of the starting blocks in each range
40
41       --limited-retry, -l
42           Sets the limited retry flag.
43
44       --force-unit-access, -f
45           Set the force-unit access flag.
46
47       --prinfow=<prinfow>, -p <prinfow>
48           Protection Information field write definition.
49
50       --prinfor=<prinfor>, -P <prinfor>
51           Protection Information field read definition.
52
53       --ref-tag=<reftag>, -r <reftag>
54           initial lba reference tag.
55
56       --expected-ref-tags=<reftag,>, -R <reftag,>
57           expected lba reference tags (comma-separated list).
58
59       --app-tag=<apptag>, -a <apptag>
60           lba app tag
61
62       --expected-app-tags=<apptag,>, -A <apptag,>
63           expected lba app tags (comma-separated list)
64
65       --app-mask=<appmask>, -m <appmask>
66           lba tag mask
67
68       --expected-app-masks=<appmask,>, -M <appmask,>
69           expected lba tag masks (comma-separated list)
70
71       --dir-type=<type>, -T <type>
72           Optional directive type. The nvme-cli only enforces the value be in
73           the defined range for the directive type, though the NVMe
74           specification (1.3a) defines only one directive, 01h, for write
75           stream identifiers.
76
77       --dir-spec=<spec>, -S <spec>
78           Optional field for directive specifics. When used with write
79           streams, this value is defined to be the write stream identifier.
80           The nvme-cli will not validate the stream requested is within the
81           controller’s capabilities.
82
83       --format=<entry-format>, -F <entry-format>
84           source range entry format
85

EXAMPLES

87       No examples yet.
88

NVME

90       Part of the nvme-user suite
91
92
93
94NVMe                              10/06/2023                      NVME-COPY(1)