diff options
| author | Zdenek Kabelac <zkabelac@redhat.com> | 2020-09-22 23:25:58 +0200 |
|---|---|---|
| committer | Zdenek Kabelac <zkabelac@redhat.com> | 2020-09-22 23:28:43 +0200 |
| commit | 3a3307c0d8029f545a31d305a23a0dec2ece65f2 (patch) | |
| tree | e05472f72b346c8715a5b6db64093cf0119b5c30 /WHATS_NEW | |
| parent | f38b7afd62533041ec68b10349169efb70c37d82 (diff) | |
| download | lvm2-3a3307c0d8029f545a31d305a23a0dec2ece65f2.tar.gz | |
vdo: enhance vdo pool extension
When user tries to extend vdo pool - he needs to go always
at least by 1 full VDO slab (defined as vdo_slab_size_mb).
To avoid all trouble around find 'workable' size - lvm2 automatically
increases the passed (or by --use-policies calculated) extension size
(and informs a user about sometimes possibly large increase as slab
size can go upto 32GiB)
With VDO users need to always 'think-big' anyway and expect such
operation to be in GiB domain range.
Diffstat (limited to 'WHATS_NEW')
| -rw-r--r-- | WHATS_NEW | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1,5 +1,6 @@ Version 2.03.11 - ================================== + Lvextend of vdo pool volumes ensure at least 1 new VDO slab is added. Use revert_lv() on reload error path after vg_revert(). Configure --with-integrity enabled. Restore lost signal blocking while VG lock is held. |