[lvm-devel] master - man: lvcreate doc passthrough

Zdenek Kabelac zkabelac at fedoraproject.org
Tue Apr 26 21:31:42 UTC 2016


Gitweb:        http://git.fedorahosted.org/git/?p=lvm2.git;a=commitdiff;h=07d92322c13e942b8a47b4370a82b70d33a6f0c8
Commit:        07d92322c13e942b8a47b4370a82b70d33a6f0c8
Parent:        d90d99b23d94dea41b65166f8bb19cb2883e527c
Author:        Zdenek Kabelac <zkabelac at redhat.com>
AuthorDate:    Mon Apr 25 13:38:24 2016 +0200
Committer:     Zdenek Kabelac <zkabelac at redhat.com>
CommitterDate: Tue Apr 26 23:29:58 2016 +0200

man: lvcreate doc passthrough

Add few more words about passthough mode.
---
 man/lvcreate.8.in |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/man/lvcreate.8.in b/man/lvcreate.8.in
index f6bb14f..fd8b3a7 100644
--- a/man/lvcreate.8.in
+++ b/man/lvcreate.8.in
@@ -219,7 +219,10 @@ If \fBwritethough\fP is specified, a write is considered complete only
 when it has been stored in the cache pool LV and on the origin LV.
 While \fBwritethrough\fP may be slower for writes, it is more
 resilient if something should happen to a device associated with the
-cache pool LV.
+cache pool LV. With \fBpassthrough\fP mode, all reads are served
+from origin LV (all reads miss the cache) and all writes are
+forwarded to the origin LV; additionally, write hits cause cache
+block invalidates. See \fBlvmcache(7)\fP for more details.
 .
 .HP
 .BR \-\-cachepolicy




More information about the lvm-devel mailing list