| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Andy Grover <agrover@redhat.com>
|
|
|
|
|
|
| |
Not supported in liblvm.
Signed-off-by: Andy Grover <agrover@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
Instead of requiring users to create a liblvm object, and then calling
methods on it, the module acquires a liblvm handle as part of
initialization. This makes it impossible to instantiate a liblvm object
with a different systemdir, but there is an alternate envvar method for
that obscure use case.
Signed-off-by: Andy Grover <agrover@redhat.com>
|
|
|
|
|
|
| |
Coding style.
Signed-off-by: Andy Grover <agrover@redhat.com>
|
|
|
|
|
|
|
|
| |
Basic example code for using python-lvm.
Originally written by agrover but fixed and improved by tasleson.
Signed-off-by: Andy Grover <agrover@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Add a Makefile.in and setup.py.in, along with changes to upper
build files as necessary.
Add --enable-python-bindings configure option
Add install_python_bindings target to toplevel makefile
Signed-off-by: Andy Grover <agrover@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
This patch set brings python-lvm up to date with the features that are currently
in lvm2app.h.
Minimal unit testing has been done at this time.
Signed-off-by: Tony Asleson <tasleson@redhat.com>
Signed-off-by: Andy Grover <agrover@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
This is a Python C module that wraps liblvm2app's functionality.
Originally written by Lars Sjostrom, I have cleaned it up extensively, and
it's working well for me. It encapsulates liblvm objects in Python objects,
and the object methods are very thin wrappers around the base liblvm
library calls.
Signed-off-by: Andy Grover <agrover@redhat.com>
|
| |
|
|
|
|
| |
New features tested in new files.
|
|
|
|
|
|
|
| |
Separate original raid test and new raid10 test,
so the old could be tested on platforms without raid10 support.
Replace test-unfriendly `ls /dev/mapper` with dmsetup ls
|
|
|
|
|
| |
If monitoring is disabled in lvm.conf, avoid its starting and preserve
DMEVENTD_MONITOR_IGNORE settings internally.
|
| |
|
|
|
|
|
| |
If the system doesn't have modprobe but happens to have modules
loaded, allow version testing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The ExecStartPost with pvscan --cache in lvm2-lvmetad.service
is not needed now as this is called transparently within the
first LVM command that queries lvmetad.
|
| |
|
|
|
|
|
|
| |
Revert changes to origin lvcreate-large test and use separate
test scripts for raid - so they can be properly skipped when
kernel doesn't support raid targets.
|
| |
|
|
|
|
| |
For thin_volumes snap_percent is meaningless.
|
|
|
|
| |
Ensure lv_snapshot_percent is used only with snapshot LVs.
|
|
|
|
|
|
| |
For now this convertions is not supported, thus disabled.
The only supported conversion for now is to create mirrored thin pools
from mirrored devices.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use same logic for lvm2api as we use lvs reporting.
data_percent is meant to be superset for snap_percent.
|
|
|
|
|
|
|
|
|
| |
It would be possible to activate a RAID LV exclusively in a cluster
volume group, but for now we do not allow RAID LVs to exist in a
clustered volume group at all. This has two components:
1) Do not allow RAID LVs to be created in a clustered VG
2) Do not allow changing a VG from single-machine to clustered
if there are RAID LVs present.
|
|
|
|
|
|
|
|
|
|
|
| |
Update code for lvconvert.
Change the lvconvert user interface a bit - now we require 2 specifiers
--thinpool takes LV name for data device (and makes the name)
--poolmetadata takes LV name for metadata device.
Fix type in thin help text -z -> -Z.
Supported is also new flag --discards for thinpools.
|
|
|
|
|
| |
Thin snapshots are individual thin volumes so they can have its own
control for rw permissions.
|
|
|
|
|
| |
Rename also subvolumes if we are inserting _tdata layer.
(Currently it breaks mirrors if it would be generic, needs fixing).
|
| |
|
|
|
|
| |
Skip tree creating when used with origin_only flag.
|
|
|
|
|
|
|
|
| |
Patch clears the flag if thin pool is stacked over mirror.
Since thin pool could be used to stack device over mirrors,
it needs resume properly i.e. mirrors with corelog which are otherwise
unconditionally skipped (for pvmove functionality).
|
|
|
|
|
|
| |
Support lv_rename without directly updating metatata.
It can save some metadata commits in some cases,
i.e. when LVs are offline.
|
|
|
|
|
| |
Check if FDs 0,1,2 are available, and in case they are missing,
use /dev/null for them.
|
|
|
|
|
|
| |
Close fds via /proc/self/fd parsing
Return error code if _close_stray_fds fails and quit application
if system is in some nonstandard state.
|
|
|
|
| |
Add missing pkg init for configure --enable-testing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MD's bitmaps can handle 2^21 regions at most. The RAID code has always
used a region_size of 1024 sectors. That means the size of a RAID LV was
limited to 1TiB. (The user can adjust the region_size when creating a
RAID LV, which can affect the maximum size.) Thus, creating, extending or
converting to a RAID LV greater than 1TiB would result in a failure to
load the new device-mapper table.
Again, the size of the RAID LV is not limited by how much space is allocated
for the metadata area, but by the limitations of the MD bitmap. Therefore,
we must adjust the 'region_size' to ensure that the number of regions does
not exceed the limit. I've added code to do this when extending a RAID LV
(which covers 'create' and 'extend' operations) and when up-converting -
specifically from linear to RAID1.
|
| |
|