diff --git a/doc/img/lvol_clone_snapshot_read.svg b/doc/img/lvol_clone_snapshot_read.svg
new file mode 100644
index 000000000..0f91d417b
--- /dev/null
+++ b/doc/img/lvol_clone_snapshot_read.svg
@@ -0,0 +1,3 @@
+
+
+
diff --git a/doc/img/lvol_clone_snapshot_write.svg b/doc/img/lvol_clone_snapshot_write.svg
new file mode 100644
index 000000000..d5da58132
--- /dev/null
+++ b/doc/img/lvol_clone_snapshot_write.svg
@@ -0,0 +1,3 @@
+
+
+
diff --git a/doc/lvol.md b/doc/lvol.md
index 9bd0c2de4..51690a4d1 100644
--- a/doc/lvol.md
+++ b/doc/lvol.md
@@ -33,6 +33,13 @@ By default lvol bdevs claim part of lvol store equal to their set size. When thi
Logical volumes support snapshots and clones functionality. User may at any given time create snapshot of existing logical volume to save a backup of current volume state.
When creating snapshot original volume becomes thin provisioned and saves only incremental differences from its underlying snapshot. This means that every read from unallocated cluster is actually a read from the snapshot and
every write to unallocated cluster triggers new cluster allocation and data copy from corresponding cluster in snapshot to the new cluster in logical volume before the actual write occurs.
+
+The read operation is performed as shown in the diagram below:
+
+
+The write operation is performed as shown in the diagram below:
+
+
User may also create clone of existing snapshot that will be thin provisioned and it will behave in the same way as logical volume from which snapshot is created.
There is no limit of clones and snapshots that may be created as long as there is enough space on logical volume store. Snapshots are read only. Clones may be created only from snapshots.