| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
Update a way we handle option passing - so we now support path and options
with space inside.
Fix dm name usage for thin pools with '-' in name.
Use new lvm.conf option thin_check_options to pass in options as string array.
|
|
|
|
|
| |
If specified - use given path without test (Path could be empty)
If autodetection is in use - check for command in available PATH.
|
|
|
|
|
| |
Since we are in error path were vg must be always NULL,
skip call of release_vg() like we do in other places.
|
| |
|
|
|
|
|
|
| |
Save some relocation entries and use directly char[].
Since we do not need yes more then 127 partitions per device, use just int8_t.
Move lvm_type_filter_destroy into local static function.
|
|
|
|
|
| |
Use 'int' counter.
Use 'bad' with goto_bad macro.
|
|
|
|
| |
Here it's not an error case - so do not push this message to stderr.
|
|
|
|
|
|
|
| |
Never return unfinished toolcontext - since error path is hit on
various stages of initialization we cannot leave it partially uninitialized,
since we would need to spread many more test across the code for config_valid.
Instead return NULL and properly release udev library resources as well.
|
| |
|
|
|
|
| |
Avoid use 32bit math for extent_size.
|
|
|
|
|
|
|
|
|
| |
If the lvcreate may decide some automagical values for a user,
try to keep the pool metadata size into 128MB range for optimal
perfomance (as suggested by Joe).
So if the pool metadata size and chunk_size were not specified,
try to select such values they would fit into 128MB size.
|
|
|
|
|
|
|
|
| |
Use thin_dump --repair suggestion in log error message
and use just warning on deactivation path without repair info
(since node has been deactivated).
Also check whether there is not 16 args for thin_check configured.
|
|
|
|
|
| |
Prevent 32bit overflow and resulting weird error reports when working
with TB sizes..
|
|
|
|
|
|
| |
Avoid using NULL pointers from udev. It seems like some older versions of udev
were improperly returning NULL in some case, so do not silently break here,
and give at least a warning to the user.
|
|
|
|
| |
Make more obvious, the origin LV for snapshot must be active.
|
| |
|
|
|
|
| |
Don't leave space on EOL.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Use libdm callback to execute thin_check before activation
thin pool and after deactivation as well.
Supporting thin_check_executable which may pass in extra options for
the tool.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add 3rd daemon return state "unknown" for lookups that are carried out
successfully but don't find the item requested.
Avoid issuing error messages when it's expected that a device that's
being looked up in lvmetad might not be there.
|
| |
|
|
|
|
|
|
| |
Hold global lock in pvscan --lvmetad. (This might need refinement.)
Add PV name to "PV gone" messages.
Adjust some log message severities. (More changes needed.)
|
|
|
|
|
|
| |
It's been unsupporte for now - and it's not going to be
implemented for thin pool kernel driver - so dropping
appearence of TRIM from libdm and lvm.
|
|
|
|
|
|
| |
Test pointers from allocation against NULL.
Error paths should be checked, some of them probably need
some extesions.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Don't use NULL return value.
|
|
|
|
| |
Adding (void) where we cannot really report an error.
|
|
|
|
| |
lvmetad client code. Fixes RHBZ 798267.
|
|
|
|
|
| |
Log errors instead of plain return 0.
Check for f->private strdup result.
|
|
|
|
|
|
|
| |
Use common code call with stack trace.
TODO: maybe the release_lv_segment_area()
should be actually able to return error code to upper level.
|
| |
|
|
|
|
|
|
|
|
|
| |
If the thin pool has disabled zeroing (created with -Zn), we at least
clear initial 4KiB of such thin volume (provisions 1st block).
If lvcreate is executed with '-an' command will abort (same way like we for
normal LV - however for normal LV option -Zn may skip clearing completely,
for thin volumes this option is not supported (applies only for pools).
|
|
|
|
|
|
|
|
|
|
|
|
| |
The OpenAIS checkpoint library is going away; therefore, cmirrord must
operate without it. The algorithms the handle the timing of when to send
a checkpoint, the determination of what to send, and which ongoing cluster
requests are relevent with respect to the checkpoints are unaffected. We
need only replace the functions that actually perform the storing/transmitting
and retrieving/receiving of the checkpoint data. Rather than store the
checkpoint data in an OpenAIS checkpoint file, we simply transmit it along
with the message that notifies the incoming node that the checkpoint is
ready.
|
|
|
|
|
|
| |
when reading VG text metadate and called from pvscan --lvmetad.
(Longer-term, that check needs moving outside of that code.)
|
| |
|
|
|
|
| |
invocation.
|
| |
|
|
|
|
| |
lvmetad is not being used.
|
| |
|
| |
|
| |
|
|
|
|
| |
alloc_policy_t, dm_string_mangling_t, percent_range_t, sign_t
|
|
|
|
|
| |
lvm_register_segtype takes ownership of segtype and call destructor
for it in error path.
|
| |
|