Commit 91782353 authored by Tomasz Zawadzki's avatar Tomasz Zawadzki Committed by Jim Harris
Browse files

doc/lvol: clarify decouple only removes single dependency 



At this times documentation give impression that decouple call
removes all dependencies for lvol. Meanwhile it only removes
a single one.

Change-Id: I2b769d47dc93a21a0331248e21059653bd741074
Signed-off-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-on: https://review.gerrithub.io/c/442848


Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarShuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
parent 6a35d0fd

doc/lvol.md

+2 −1
Original line number Diff line number Diff line
@@ -64,7 +64,8 @@ Blobs can be inflated to copy data from backing devices (e.g. snapshots) and all 


## Decoupling {#lvol_decoupling}



Blobs can be decoupled from all dependencies by copying data from backing devices (e.g. snapshots) for all allocated clusters. Remaining unallocated clusters are kept thin provisioned.

Blobs can be decoupled from their parent blob by copying data from backing devices (e.g. snapshots) for all allocated clusters. Remaining unallocated clusters are kept thin provisioned.

Note: When decouple is performed, only single dependency is removed. To remove all dependencies in a chain of blobs depending on each other, multiple calls need to be issued.



# Configuring Logical Volumes