Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=23ef67776210ad6c55f4d…
Commit: 23ef67776210ad6c55f4dd7475b806337140c513
Parent: 5dbe2fdd9dd783c2911a5375d6fdec86118af280
Author: Marian Csontos <mcsontos(a)redhat.com>
AuthorDate: Fri Dec 11 12:16:16 2020 +0100
Committer: Marian Csontos <mcsontos(a)redhat.com>
CommitterDate: Fri Dec 11 12:16:16 2020 +0100
configure: update
---
aclocal.m4 | 10 ++++++----
configure | 2 +-
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/aclocal.m4 b/aclocal.m4
index 3e0fbd38d..7524c8313 100644
--- a/aclocal.m4
+++ b/aclocal.m4
@@ -496,12 +496,14 @@ AC_DEFUN([AM_PATH_PYTHON],
m4_default([$3], [AC_MSG_ERROR([no suitable Python interpreter found])])
else
- dnl Query Python for its version number. Getting [:3] seems to be
- dnl the best way to do this; it's what "site.py" does in the standard
- dnl library.
+ dnl Query Python for its version number. Although site.py simply uses
+ dnl sys.version[:3], printing that failed with Python 3.10, since the
+ dnl trailing zero was eliminated. So now we output just the major
+ dnl and minor version numbers, as numbers. Apparently the tertiary
+ dnl version is not of interest.
AC_CACHE_CHECK([for $am_display_PYTHON version], [am_cv_python_version],
- [am_cv_python_version=`$PYTHON -c "import sys; sys.stdout.write(sys.version[[:3]])"`])
+ [am_cv_python_version=`$PYTHON -c "import sys; print('%u.%u' % sys.version_info[[:2]])"`])
AC_SUBST([PYTHON_VERSION], [$am_cv_python_version])
dnl Use the values of $prefix and $exec_prefix for the corresponding
diff --git a/configure b/configure
index 29d19f249..4c38cbebb 100755
--- a/configure
+++ b/configure
@@ -11962,7 +11962,7 @@ $as_echo_n "checking for $am_display_PYTHON version... " >&6; }
if ${am_cv_python_version+:} false; then :
$as_echo_n "(cached) " >&6
else
- am_cv_python_version=`$PYTHON -c "import sys; sys.stdout.write(sys.version[:3])"`
+ am_cv_python_version=`$PYTHON -c "import sys; print('%u.%u' % sys.version_info[:2])"`
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_python_version" >&5
$as_echo "$am_cv_python_version" >&6; }
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=7691213a91ca7cc2d5518…
Commit: 7691213a91ca7cc2d5518db31d04c8afa74622e7
Parent: 9b3458d5a945302a68e4f5ed3011f01677411e9b
Author: Zdenek Kabelac <zkabelac(a)redhat.com>
AuthorDate: Mon Dec 7 17:04:49 2020 +0100
Committer: Zdenek Kabelac <zkabelac(a)redhat.com>
CommitterDate: Tue Dec 8 20:32:34 2020 +0100
man: update lvmvdo
Fix vdo example.
Update some sentences.
---
man/lvmvdo.7_main | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/man/lvmvdo.7_main b/man/lvmvdo.7_main
index 39dee3914..474d6dd73 100644
--- a/man/lvmvdo.7_main
+++ b/man/lvmvdo.7_main
@@ -16,7 +16,7 @@ and also eliminates any blocks of all zeroes.
With deduplication, instead of writing the same data more than once, VDO detects and records each
duplicate block as a reference to the original
-block. VDO maintains a mapping from logical block addresses (used by the
+block. VDO maintains a mapping from Logical Block Addresses (LBA) (used by the
storage layer above VDO) to physical block addresses (used by the storage
layer under VDO). After deduplication, multiple logical block addresses
may be mapped to the same physical block address; these are called shared
@@ -59,7 +59,7 @@ VDOPoolLV
.br
VDO pool LV
.br
-A pool for virtual VDOLV(s) with the size of used VDODataLV.
+A pool for virtual VDOLV(s), which are the size of used VDODataLV.
.br
Only a single VDOLV is currently supported.
.TP
@@ -72,7 +72,7 @@ Created from VDOPoolLV.
Appears blank after creation.
.SH VDO USAGE
The primary methods for using VDO with lvm2:
-.SS 1. Create VDOPoolLV with VDOLV
+.SS 1. Create a VDOPoolLV and a VDOLV
Create a VDOPoolLV that will hold VDO data, and a
virtual size VDOLV that the user can use. If you do not specify the virtual size,
then the VDOLV is created with the maximum size that
@@ -97,9 +97,9 @@ operation.
# lvcreate --type vdo -n vdo0 -L 10G -V 100G vg/vdopool0
# mkfs.ext4 -E nodiscard /dev/vg/vdo0
.fi
-.SS 2. Create VDOPoolLV from conversion of an existing LV into VDODataLV
-Convert an already created or existing LV into a volume that can hold
-VDO data and metadata (volume referenced by VDOPoolLV).
+.SS 2. Convert an existing LV into VDOPoolLV
+Convert an already created or existing LV into a VDOPoolLV, which is a volume
+that can hold data and metadata.
You will be prompted to confirm such conversion because it \fBIRREVERSIBLY
DESTROYS\fP the content of such volume and the volume is immediately
formatted by \fBvdoformat\fP(8) as a VDO pool data volume. You can
@@ -238,7 +238,8 @@ a long time.
.fi
.SS 8. Component activation of a VDODataLV
You can activate a VDODataLV separately as a component LV for examination
-purposes. It activates the data LV in read-only mode, and the data LV cannot be modified.
+purposes. The activation of the VDODataLV activates the data LV in read-only mode,
+and the data LV cannot be modified.
If the VDODataLV is active as a component, any upper LV using this volume CANNOT
be activated. You have to deactivate the VDODataLV first to continue to use the VDOPoolLV.
@@ -280,7 +281,7 @@ it hits the processing of the VDO Pool LV layer.
.I Example
.nf
-# lvcreate -L 5G -V 10G -n vdo1 vg/vdopool
+# lvcreate --type vdo -L 5G -V 10G -n vdo1 vg/vdopool
# lvcreate --type cache-pool -L 1G -n cachepool vg
# lvconvert --cache --cachepool vg/cachepool vg/vdo1
# lvconvert --uncache vg/vdo1
@@ -292,13 +293,13 @@ and takes a considerable amount of time and CPU.
Unless you really need it, you should avoid using discard.
When a block device is going to be rewritten,
-block will be automatically reused for new data.
-Discard is useful in situations when it is known that the given portion of a VDO LV
+its blocks will be automatically reused for new data.
+Discard is useful in situations when user knows that the given portion of a VDO LV
is not going to be used and the discarded space can be used for block
provisioning in other regions of the VDO LV.
For the same reason, you should avoid using mkfs with discard for
a freshly created VDO LV to save a lot of time that this operation would
-take otherwise as device after create empty.
+take otherwise as device is already expected to be empty.
.SS 6. Memory usage
The VDO target requires 370 MiB of RAM plus an additional 268 MiB
per each 1 TiB of physical storage managed by the volume.
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=9b3458d5a945302a68e4f…
Commit: 9b3458d5a945302a68e4f5ed3011f01677411e9b
Parent: a2affffed558899af563b790eaf5112b8c7e5bd5
Author: David Teigland <teigland(a)redhat.com>
AuthorDate: Wed Dec 2 15:29:21 2020 -0600
Committer: David Teigland <teigland(a)redhat.com>
CommitterDate: Wed Dec 2 15:29:21 2020 -0600
man lvmcache: add writecache cleaner info
---
man/lvmcache.7_main | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/man/lvmcache.7_main b/man/lvmcache.7_main
index 37d0e3359..85d4d9e34 100644
--- a/man/lvmcache.7_main
+++ b/man/lvmcache.7_main
@@ -303,6 +303,16 @@ afterwards. Some underlying devices perform better with fua, some with
nofua. Testing is necessary to determine which.
Applicable only to persistent memory.
+.IP \[bu] 2
+cleaner = 0|1
+
+Setting cleaner=1 enables the writecache cleaner mode in which data is
+gradually flushed from the cache. If this is done prior to detaching the
+writecache, then the splitcache command will have little or no flushing to
+perform. If not done beforehand, the splitcache command enables the
+cleaner mode and waits for flushing to complete before detaching the
+writecache. Adding cleaner=0 to the splitcache command will skip the
+cleaner mode, and any required flushing is performed in device suspend.
.SS dm-cache with separate data and metadata LVs