mirror of https://gitee.com/openkylin/linux.git
7431b7835f
Add the dm-clone target, which allows cloning of arbitrary block devices. dm-clone produces a one-to-one copy of an existing, read-only source device into a writable destination device: It presents a virtual block device which makes all data appear immediately, and redirects reads and writes accordingly. The main use case of dm-clone is to clone a potentially remote, high-latency, read-only, archival-type block device into a writable, fast, primary-type device for fast, low-latency I/O. The cloned device is visible/mountable immediately and the copy of the source device to the destination device happens in the background, in parallel with user I/O. When the cloning completes, the dm-clone table can be removed altogether and be replaced, e.g., by a linear table, mapping directly to the destination device. For further information and examples of how to use dm-clone, please read Documentation/admin-guide/device-mapper/dm-clone.rst Suggested-by: Vangelis Koukis <vkoukis@arrikto.com> Co-developed-by: Ilias Tsitsimpis <iliastsi@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> |
||
---|---|---|
.. | ||
cache-policies.rst | ||
cache.rst | ||
delay.rst | ||
dm-clone.rst | ||
dm-crypt.rst | ||
dm-dust.txt | ||
dm-flakey.rst | ||
dm-init.rst | ||
dm-integrity.rst | ||
dm-io.rst | ||
dm-log.rst | ||
dm-queue-length.rst | ||
dm-raid.rst | ||
dm-service-time.rst | ||
dm-uevent.rst | ||
dm-zoned.rst | ||
era.rst | ||
index.rst | ||
kcopyd.rst | ||
linear.rst | ||
log-writes.rst | ||
persistent-data.rst | ||
snapshot.rst | ||
statistics.rst | ||
striped.rst | ||
switch.rst | ||
thin-provisioning.rst | ||
unstriped.rst | ||
verity.rst | ||
writecache.rst | ||
zero.rst |