| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
before equal op
|
| |
|
| |
|
| |
|
|
|
|
| |
objects that satisfy the report selection
|
|
|
|
| |
selections
|
| |
|
| |
|
| |
|
|
|
|
| |
and SIZE
|
| |
|
| |
|
| |
|
|
|
|
| |
Few missed unconverted dm_malloc/free calls.
|
|
|
|
|
|
| |
Initialized attrs so analyzers are less confused
(since currently our method calls should always initialize attrs on
return).
|
| |
|
|
|
|
|
| |
Since we intentionaly do not want to check them,
cast result values to void.
|
|
|
|
|
|
| |
If we would have been missing origin here, it would
be an internal error - since these values are validated
earlier.
|
|
|
|
| |
Ensure str is not NULL for analyzer.
|
|
|
|
| |
Cast data_extents to 64bit so calculation is in 64b arithmetic.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support upto 3 levels os nesting signal blocking.
As of today - code blocks signals immediatelly when it opens
VG in read-write mode - this however makes current prompt usage
then partially unusable since user may not 'break' command
during prompt (something most user would expect).
Until a better fix for prompting is implemented, put in support
for signal nesting - thus when prompt enables signal acceptance,
make it possible to really break command at this point.
|
|
|
|
|
|
| |
Adding log_sys_debug for eventual logging of system errors.
(Using debug level, since currently signal handling functions
do not fail when any error is encoutered).
|
|
|
|
|
| |
Use sigint_allow/restore function instead of duplicating code
and switch to use only sigactiction based signal handling.
|
|
|
|
| |
"DIST_TARGET" should be "DISTCLEAN_TARGET"
|
|
|
|
| |
locking/file_locking.c:162:2: warning: implicit declaration of function ‘init_signals’
|
|
|
|
|
| |
The decode_flags() function does not yet know about the
LCK_REVERT_MODE flag.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The sysinit.target is ordered even before sockets.target and there
may be situations in which the lvmetad is needed early, for example
in rescue.target to activate some LVs on which mountpoints reside.
Also, like in the case of rescue.target, the sockets.target is not
pulled in (unless some other service pulls it in explicitly).
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1087586#c26
for the summary of the problem.
|
|
|
|
| |
unwanted start of dmeventd was caused by seg_monitor status.
|
|
|
|
|
|
| |
Drop compilation of modules_needed and add_target_lin
function when compiled without devmapper support.
Cleanup surrounding ifdefs.
|
| |
|
|
|
|
|
| |
Drop header inclusion - this file is already included.
Shorten code.
|
|
|
|
|
| |
Leave addition of unknown segment to table as internal error.
Do not replace unknown segment with error device.
|
|
|
|
|
|
| |
Commit 1af05a7a166a470d1b9d86f88fdc64c2d984124b was incorrect.
Generated files from configure could be only distclean-ed.
(in-release fix)
|
|
|
|
|
| |
Print 'X' also when lv_info() fails.
(i.e. compilation with --disable-ioctl)
|
|
|
|
| |
Always pass fully initialized timeval struct to select.
|
|
|
|
| |
Fix compilation when configured with --disable-devmapper option.
|
| |
|
|
|
|
|
|
| |
The correct name for disable ioctl option is --disable-ioctl
(--disable-driver never worked)
Also sort scripts generated files alphabetically.
|
|
|
|
|
|
| |
When quering for dmeventd monitoring status, check first
if lvm2 is configured to monitor to avoid unwanted start
of dmeventd process for answering monitoring status.
|
| |
|
|
|
|
| |
Test more code paths for lvscan & lvdisplay
|
|
|
|
| |
No reason to check for VALID in extra if.
|
|
|
|
|
|
|
|
| |
When showing ACTIVE status for snapshot's origin,
avoid testing all its snapshot - it's not useful
to tell user origin is inactivate, while it's clearly
available and running - just one of its snapshot leg
is invalid...
|
|
|
|
|
|
|
|
| |
Relocate info from thin pool and thin volume segments
to proper code section for segments.
Add discards and thin count status info.
Info is shown with 'lvdisplay --maps' (like for other segments).
|
|
|
|
|
|
|
|
|
|
| |
For percentage display we need -tpool - so check for layered
device presence here instead of plain pool device.
Also update 'info' - so when pool is 'available' we
display open count for -tpool device instead of mostly
irrelevant pool.
TODO: Maybe we should actually display this open info always?
(even when just -tpool is available, but pool is not)
|
|
|
|
|
| |
When displaying segments (lvdisplay --maps)
show monitoring status when supported by segment.
|