| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
This reverts commit abcab54cca4b4f9ff157a5f51718c69ffdf34c7a.
Dmesg is not uploaded on machines except on F19.
|
| | |
|
| | |
|
| |
|
|
|
| |
Update test for recent updates to support unalligned sizes
and extension of reduced volume.
|
| |
|
|
| |
Keep logging readable and fflush stdout before printing to stderr.
|
| |
|
|
|
|
|
| |
Relocate hyphen code from lvm main into lvm_run_command()
so all command and library user will have it.
Update WHATS_NEW with missing changes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use of display_lvname() in plain log_debug() may accumulate memory in
command context mempool. Use instead small ringbuffer which allows to
store cuple (10 ATM) names so upto 10 full names can be used at one.
We are not keeping full VG/LV names as it may eventually consume larger
amount of RAM resouces if vgname is longer and lots of LVs are in use.
Note: if there would be ever needed for displaing more names at once,
the limit should be raised (e.g. log_debug() would need to print more
then 10 LVs on a single line).
|
| |
|
|
|
|
|
|
|
| |
With thin-pool kernel target module 1.13 it's now support usage of
external origin with sizes which are not 'alligned' with chunk size
of thin-pool.
Enable lvm2 support for this and also fix reporting of data_percent
usage for case sizes are not alligned.
|
| |
|
|
|
|
| |
Drop check which has prevented resize of reduce thin volume with
external origin. User is supposed to use 'zeroing' to get 'clean'
chunks.
|
| |
|
|
|
| |
Support thin-pool tree node with activation in read-only mode.
(Native kernel API).
|
| |
|
|
| |
so it can be used elsewhere.
|
| | |
|
| |
|
|
| |
More efficient with same result here.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
component is suspended
Note that this is just a quick fix and it needs more robust fix to
encompass any combination, not just the (old) snapshot one!
This started with this report:
https://bugzilla.redhat.com/show_bug.cgi?id=1219222
If we have devices/ignore_suspended_devices=1 set based on which we
filter out suspended devices as unusable (or if we ignore suspended
devices by force, e.g. during lvconvert called from dmeventd) and
when we have snapshot and snapshot origin devices in the play, we
need to look at their components unerneath (*-real and *-cow) to
check if they're not suspended. If they are, the snapshot/snapshot
origin is not usable as well and hence it needs to be filtered out
by filter-usable.c code which does suspended device filtering.
Not going into much details here, more details are in the bugzilla
mentioned above. However, this is a quick fix since snapshot
and this exact situation is not the only one. So this is
something that needs to be revisited and fixed properly
with full dm tree and checking the whole stack to state
whether the device at the very top is usable or not.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of CFG_DEFAULT_UNDEFINED and causing segfault
This patch fixes segfault which was caused by incorrectly marking some
settings CFG_DEFAULT_COMMENTED instead of CFG_DEFAULT_UNDEFINED - the
ones which have NULL default value, hence they're really undefined.
A regression caused by a98ceceb1d101f0b19a6115f406e23f13feab5ae.
For example:
$ lvmconfig log/file
file="/a"
Before this patch:
$ lvmconfig --type diff
Segmentation fault (core dumped)
With this patch applied:
$ lvmconfig --type diff
log {
file="/a"
}
The same applies for these settings:
log/activate_file
global/library_dir
global/system_id_file
<disk_area>/disk_area_id
There were also other settings with NULL default value and marked as
CFG_DEFAULT_COMMENTED instead of CFG_DEFAULT_UNDEFINED, but they were
cfg_array config settings where the NULL value was not causing segfault
(NULL == empty array).
|
| |
|
|
| |
Which returns the string set by set_cmd_name().
|
| |
|
|
| |
So that it can be used from other lib code.
|
| |
|
|
|
| |
and improve the existing text about existing
activation options.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Just as 'e' means activation with an exclusive lock,
add an 's' to mean activation with a shared lock.
This allows the existing but implicit behavior of '-ay'
of clvm LVs to be specified explicitly. For local VGs,
asy simply means ay, just like aey means ay.
For local VGs, ay == aey == asy
For clvm VGs, ay == asy, aey == aey, asy == asy
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The hyphens are removed from long option names before
being read. This means that:
- Option name specifications in args.h must not include hyphens.
(The hyphen in 'use-policies' is removed.)
- A user can include hyphens anywhere in the option name.
All the following are equivalent:
--vgmetadatacopies,
--vg-metadata-copies,
--v-g-m-e-t-a-d-a-t-a-c-o-p-i-e-s-
|
| |
|
|
| |
New variants use the clearer function names from the kernel.
|
| |
|
|
| |
for changing the cache mode on an existing LV.
|
| |
|
|
| |
Enhance traced output.
|
| |
|
|
| |
Print reason for failing ioctl if thin pool message fails.
|
| |
|
|
|
| |
Second const is unneeded.
Also always create whole array with MAX elements.
|
| |
|
|
| |
Avoid using 'static' variable within threaded environmnent for debuging.
|
| | |
|
| |
|
|
|
| |
Drop unused pthread canceling as well as DEBUG printing in signal
handler.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
and rdynamic. They are not needed.
|
| |
|
|
|
|
|
|
| |
lvmetad_init() should not be called with open connection to the daemon.
Doing so is considered to be an internall error within lvm2 code.
Such coincidence can't occur within current code. Let's assure us it won't
ever happen.
|
| |
|
|
|
|
|
|
| |
Some of descritpions were misleading at least. Some were completely
off the reality.
lvmetad_init doesn't re-establish or initialise a connection
lvmetad_active and lvmetad_connect_or_warn can do so.
|
| |
|
|
|
| |
Clear some stale information, and give a suggestion to use
a metadata size of 1GiB.
|
| | |
|
| | |
|
| |
|
|
|
| |
A bit hacky since it expects PID_DIR == DEFAULT_RUN_DIR for now,
just to check whether it fixes startup clvmd sync problem.
|
| |
|
|
|
|
| |
Update check for raid array being in sync - getting somewhat complex.
It's another way to fight with problems in:
https://bugzilla.redhat.com/show_bug.cgi?id=1210637
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
commit c069aff21b1450923b59e98ab709a5e667cdcda9
commit 8af5f54824f889c438104625dbe159f6e8dedbc4
|
| |
|
|
|
|
| |
Testing errno value without explicitly setting to
zero in before the strtoul call may lead to
unexpected failures.
|
| |
|
|
|
|
| |
Testing errno value without explicitly setting to
zero in before the strtoul call may lead to
unexpected failures.
|
