ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc/lvol: clarify decouple only removes single dependency

Browse Source 
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: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-on: https://review.gerrithub.io/c/442848
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
Tomasz Zawadzki 2019-01-31 03:57:37 -05:00 committed by Jim Harris
parent 6a35d0fd13
commit 9178235324
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/lvol.md
View File

@ -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