1 .TH LCTL-SNAPSHOT_CREATE 8 "2017-05-13" Lustre "configuration utilities"
3 lctl-snapshot_create \- create Lustre snapshot
6 .B lctl snapshot_create \fR[-b | --barrier [on | off]] [-c | --comment comment]
7 {-F | --fsname fsname} [-h | --help] {-n | --name ssname}
8 [-r | --rsh remote_shell] [-t | --timeout timeout]
11 Create snapshot with the given name. The tool loads system configuration from
17 section. Then, the snapshot pieces are created on every Lustre target
21 .BR -b ", " --barrier " [" on | off ]
22 Set write barrier on all MDTs before creating the snapshot. The default value is
24 If you are confident about the system consistency, or not require the full
25 consistency and want to avoid blocking applications when creating the snapshot,
26 then you can specify barrier
28 That will save your time of creating the snapshot. If the barrier is
30 then the timeout of the barrier can be specified via
32 option as described in the subsequent section.
34 .BR -c ", " --comment " "\fIcomment
35 Add an optional comment to the
37 request. The comment can include anything to describe what the snapshot is for
38 or for a reminder. The comment can be shown via
41 .BR -F ", " --fsname " "\fIfsname
47 .BR -n ", " --name " "\fIssname
48 The snapshot's name must be specified. It follows the general ZFS snapshot name
49 rules, such as the max length is 256 bytes, cannot conflict with the reserved
52 .BR -r ", " --rsh " "\fIremote_shell
53 Specify a shell to communicate with remote targets. The default value is
55 It is the system admin's duty to guarantee that the specified
57 works well among targets without password authentication.
59 .BR -t ", " --timeout " "\fItimeout
64 specifies the write barrier's lifetime in second. The default vaule is 30.
67 .B lctl-snapshot-create
75 .BR lctl-snapshot-destroy (8),
76 .BR lctl-snapshot-modify (8),
77 .BR lctl-snapshot-list (8),
78 .BR lctl-snapshot-mount (8),
79 .BR lctl-snapshot-umount (8)