Lines Matching full:clone

4 dm-clone
10 dm-clone is a device mapper target which produces a one-to-one copy of an
15 The main use case of dm-clone is to clone a potentially remote, high-latency,
26 When the cloning completes, the dm-clone table can be removed altogether and be
29 The dm-clone target reuses the metadata library used by the thin-provisioning
56    clone of the source device.
68 dm-clone divides the source and destination devices in fixed sized regions.
72 The region size is configurable when you first create the dm-clone device. The
92 dm-clone interprets a discard request to a range that hasn't been hydrated yet
97 If the destination device supports discards, then by default dm-clone will pass
103 dm-clone copies continuously from the source to the destination device, until
108 any one time. Moreover, dm-clone takes into account user I/O traffic going to
114 dm-clone employs dm-kcopyd for copying portions of the source device to the
118 dm-clone trying to batch together contiguous regions, so we copy the data in
129 dm-clone device behaves like a physical disk that has a volatile write cache. If
141    clone <metadata dev> <destination dev> <source dev> <region size>
154                   passed to dm-clone
155  core args        Key/value pairs passed to dm-clone, e.g. `hydration_threshold
162  no_hydration         Create a dm-clone instance with background hydration
187    <clone metadata mode>
202  clone metadata mode     ro if read-only, rw if read-write
228 Clone a device containing a file system
231 1. Create the dm-clone device.
235     dmsetup create clone --table "0 1048576000 clone $metadata_dev $dest_dev \
238 2. Mount the device and trim the file system. dm-clone interprets the discards
243     mount /dev/mapper/clone /mnt/cloned-fs
250     dmsetup message clone 0 enable_hydration
252 4. When the hydration finishes, we can replace the dm-clone table with a linear
257     dmsetup suspend clone
258     dmsetup load clone --table "0 1048576000 linear $dest_dev 0"
259     dmsetup resume clone
286 We explored the following alternatives before implementing dm-clone:
319    un-provisioned/not-yet-cloned areas the same way as dm-clone does.
333    LV as dm-clone's destination device.