diff options
| author | Zdenek Kabelac <zkabelac@redhat.com> | 2021-10-01 16:19:53 +0200 |
|---|---|---|
| committer | Zdenek Kabelac <zkabelac@redhat.com> | 2021-10-06 15:42:53 +0200 |
| commit | 5ea426e65628218569ede461312d80ba5d1c50fb (patch) | |
| tree | 678d0505ce7263cb1fd4df5e2c9cfc387d7f6099 /WHATS_NEW | |
| parent | 98c57f7ce44788f22499f10f8d6c3f320869aa16 (diff) | |
| download | lvm2-5ea426e65628218569ede461312d80ba5d1c50fb.tar.gz | |
archiving: refactor code to allocate less memory
Do not store full path with each archived name reduces memory usage if
the directory has thousands of entries and just add 'dir' path when
needed.
Also emit info print message to a user if the total size of archived
files for a VG is more then 128MiB or 8192 files.
TODO: Consider wheather adding a new 'lvm.conf archive{option}' to support
trimming these wild archive sizes can make situation better.
We already support retain_min && retain_days - but if user is
generating too many and too large archives with minutes - maybe archiving
should be disabled by a user - as it's not producing anything largely usable
and just slows-down command ??
If we add 'retain_max & retain_max_size' the condition will go against
each other and we need to chose priorities.
mm
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.14 - ================================== + Print info message with too many or too large archived files. Reduce metadata readings during scanning phase. Optimize computation of crc32 check sum with multiple PVs. Enhance recover path on cache creation failure. |