| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The autoactivation property can be specified in lvcreate
or vgcreate for new LVs/VGs, and the property can be changed
by lvchange or vgchange for existing LVs/VGs.
--autoactivation n|y
disables|enables autoactivation of a VG or LV.
Autoactivation is enabled by default, which is consistent with
past behavior. (The disabled state is stored as a new flag
in the VG metadata, and the absence of the flag allows
autoactivation.)
If autoactivation is disabled for the VG, then no LVs in the VG
will be autoactivated (the LV autoactivation property will have
no effect.) When autoactivation is enabled for the VG, then
autoactivation can be controlled on individual LVs.
The state of this property can be reported for LVs/VGs using
the "-o autoactivation" option in lvs/vgs commands, which will
report "enabled", and "" for the disabled state.
Previous versions of lvm do not recognize this property. Since
autoactivation is enabled by default, the disabled setting will
have no effect in older lvm versions. If the VG is modified by
older lvm versions, the disabled state will also be dropped from
the metadata.
The autoactivation property is an alternative to using the lvm.conf
auto_activation_volume_list, which is still applied to to VGs/LVs
in addition to the new property.
If VG or LV autoactivation is disabled either in metadata or in
auto_activation_volume_list, it will not be autoactivated.
To determine the effective autoactivation behavior for a specific
LV, multiple settings would need to be checked:
the VG autoactivation property, the LV autoactivation property,
the auto_activation_volume_list. The "activation skip" property
would also be relevant, since it applies to both normal and auto
activation.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Switch to plain 'kill' we should no longer need SIGKILL
as polling can be interrupted.
Resolve problem in aux wait_pvmove_lv_ready() that was using
lvm command to check for UUID - but this was interferring with
VG lock and it's been delaying confirmation.
So reducing slow-down of test - so it can run faster.
|
|
|
|
| |
Internally lvm2 is not using versioning for device-mapper.
|
| |
|
|
|
|
| |
Avoid scanning for source duplicates in various build dirs.
|
| |
|
|
|
|
|
|
| |
Enhance handling of interruptions of polling process and lvmpoll daemon.
Daemon should now react much faster on interrups (i.e. shutdown
sequence) and avoid taking lenghty sleep waiting on pvmove signaling.
|
|
|
|
|
| |
When checking for mirror percentage with WAITEVENT (i.e. during pvmove)
handle intrruption (^C) of such wait.
|
|
|
|
|
| |
Avoid sleeping in pselect when thread missed reap() handling.
This speedup handling of daemon shutdown sequences.
|
|
|
|
|
|
|
|
| |
If we are signaled with SIGTERM it should be at least as good
as with SIGINT - as the command should stop ASAP.
So when lvm2 command allows signal handling we also
enable SIGTERM handling. If there are some other signals
we should handle equally - we could just extend array.
|
|
|
|
| |
Missed support for --yes with 'lvreduce' to answer 'y' to prompt.
|
|
|
|
|
|
|
|
|
| |
ABI dumper does not like missing enum/union/struct names,
so add them with _e, _u suffix.
Usage reference:
https://doc.dpdk.org/guides-16.04/contributing/versioning.html
|
| |
|
| |
|
|
|
|
|
| |
Simple check produced library has the latest symbol as well as its versioned
older version with check for dm_stats_create_region().
|
|
|
|
|
|
|
| |
Avoid emitting Local symbol and sort symbols from
start and add dependency on previous version
Should not change anything, just better followup
linkage guidlines.
|
|
|
|
|
|
| |
Version is only needed for dm_task_get_info().
dm_task_get_info_with_deferred_remove() shall be compiled for
non-versioned library as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gcc10 introduced different strategy how to build
shared libraries with their new LTO optimizer.
Insired by:
https://akkadia.org/drepper/symbol-versioning
https://sourceware.org/pipermail/elfutils-devel/attachments/20200414/1c0c2903/attachment.bin
https://github.com/InBetweenNames/gentooLTO/issues/459
https://github.com/linux-rdma/rdma-core/blob/master/util/symver.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200
|
|
|
|
|
|
| |
Devices are not in a steady state during system init,
so hints are repeatedly invalidated, and hardly used,
so maintaining them is wasted effort.
|
| |
|
| |
|
|
|
|
|
|
| |
Add missing description for profile usage with cache pool.
List cache-pools as first option for dm-cache as it provides
better performance and more functionality over cachevols.
|
|
|
|
| |
Add missing writecache type into man pages.
|
|
|
|
| |
Avoid using lvm header for libdm build.
|
|
|
|
| |
No need for versioning history in internal version.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not all libc (like musl, uclibc dietlibc) libraries support full symbol
version resolution in runtime like glibc.
Add support to not generate symbol versions when compiling against them.
Additionally libdevmapper.so was broken when compiled against
uclibc. Runtime linker loader caused calling dm_task_get_info_base()
function recursively, leading to segmentation fault.
Introduce --with-symvers=STYLE option, which allows to choose
between gnu and disabled symbol versioning. By default gnu symbol
versioning is used.
__GNUC__ check is replaced now with GNU_SYMVER.
Additionally ld version script is included only in
case of gnu option, which slightly reduces output size.
Providing --without-symvers to configure script when building against
uclibc library fixes segmentation fault error described above, due to
lack of several versions of the same symbol in libdevmapper.so
library.
Based on:
https://patchwork.kernel.org/project/dm-devel/patch/20180831144817.31207-1-m.niestroj@grinn-global.com/
Suggested-by: Marcin Niestroj <m.niestroj@grinn-global.com>
|
|
|
|
|
| |
Check different sleep properties for lvmpolld.
Use aux remove_dm_devs.
|
|
|
|
|
| |
Add function to remove DM devices and dies
if some device can't be removed.
|
| |
|
|
|
|
| |
Skip test with LVM_TEST_DEVDIR != /dev
|
| |
|
| |
|
|
|
|
|
| |
We need to stop pvmove while still in progress,
so restart lvmpolld after pvmoving devices are gone
|
|
|
|
| |
Try losetup few times in loop if we can succeed.
|
|
|
|
| |
During debugging this prefix was unintentionally lost, restore.
|
|
|
|
|
| |
Actually make sure which 'test' binary is executed.
Since we used to have 'test' binary in tests.
|
|
|
|
|
|
|
|
| |
Looks like there was some missed versioning increase during devel.
So with kernel >= 4.18 version 1.19 is enough to look like 1.20
However backported 1.19 targets seems to not provide all
the capabilities.
|
|
|
|
| |
Use thin-pool target version 1.20 for changed behavior.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Test has to use PV with suffix pv[0..9] otherwise
it's ignored by test suite filter.
Better fix for VG names to use prefix LVMTEST.
Skip the test for runs without LVM_TEST_DEVDIR != /dev
|
|
|
|
| |
Newer thin-pool handle metadata read-only recovery better.
|
|
|
|
|
| |
Always use blkid without caching to avoid poluting
cache stored in /run/blkid or /etc on older distros
|
| |
|
|
|
|
| |
Wrapper for slowed version of mdadm --assemble
|
| |
|
|
|
|
| |
These test do not test polling, so skip them for lvmpolld pass.
|