Lines Matching refs:origin

11 *) To merge a snapshot of a block device back into the snapshot's origin
19 the origin device.
23 snapshot, snapshot-origin, and snapshot-merge.
25 *) snapshot-origin <origin>
33 *) snapshot <origin> <COW device> <persistent?> <chunksize>
35 A snapshot of the <origin> block device is created. Changed chunks of
38 from <origin> for unchanged data.  <COW device> will often be
39 smaller than the origin and if it fills up the snapshot will become
49 * snapshot-merge <origin> <COW device> <persistent> <chunksize>
53 "snapshot-origin" target and must not be loaded if the "snapshot-origin"
54 is still present for <origin>.
58 procedure, and merges these chunks back into the <origin>.  Once merging
59 has started (in the background) the <origin> may be opened and the merge
60 will continue while I/O is flowing to it.  Changes to the <origin> are
75    source volume), whose table is replaced by a "snapshot-origin" mapping
90 volumeGroup-base: 0 2097152 snapshot-origin 254:11
101 A merging snapshot assumes the role of the "snapshot-origin" while
102 merging.  As such the "snapshot-origin" is replaced with
104 device is renamed to <origin name>-cow to aid LVM2's cleanup of the
109 A snapshot will merge into its origin with the following command: