Lines Matching full:origin

12 -  To merge a snapshot of a block device back into the snapshot's origin
20 the origin device.
24 snapshot, snapshot-origin, and snapshot-merge.
26 -  snapshot-origin <origin>
34 -  snapshot <origin> <COW device> <persistent?> <chunksize>
37 A snapshot of the <origin> block device is created. Changed chunks of
40 from <origin> for unchanged data.  <COW device> will often be
41 smaller than the origin and if it fills up the snapshot will become
55 snapshot-origin or snapshot-merge target must be suspended. A failure to
56 suspend the origin target could result in data corruption.
65    down to the snapshot-origin's underlying device.  This doesn't cause
66    copy-out to the snapshot exception store because the snapshot-origin
73 -  snapshot-merge <origin> <COW device> <persistent> <chunksize>
78 "snapshot-origin" target and must not be loaded if the "snapshot-origin"
79 is still present for <origin>.
83 procedure, and merges these chunks back into the <origin>.  Once merging
84 has started (in the background) the <origin> may be opened and the merge
85 will continue while I/O is flowing to it.  Changes to the <origin> are
100    source volume), whose table is replaced by a "snapshot-origin" mapping
115   volumeGroup-base: 0 2097152 snapshot-origin 254:11
126 A merging snapshot assumes the role of the "snapshot-origin" while
127 merging.  As such the "snapshot-origin" is replaced with
129 device is renamed to <origin name>-cow to aid LVM2's cleanup of the
134 A snapshot will merge into its origin with the following command::
166     LV      VG          Attr   LSize Origin  Snap%  Move Log Copy%  Convert
178     LV      VG          Attr   LSize Origin  Snap%  Move Log Copy%  Convert
195     LV      VG          Attr   LSize Origin  Snap%  Move Log Copy%  Convert