summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* spec: Profiles are not %confi(noreplace)for-masterMarian Csontos2016-09-141-7/+7
| | | | These files are just examles and should not be edited by user.
* tests: Revert "tests: not redirect strderr to stdout"Zdenek Kabelac2016-09-131-5/+2
| | | | | | | This reverts commit 5314d36f3d186efb05a051e80444332f743194ef. Ok - some tests do look for 'stderr' output of 'not' commands. So let's keep existing functionality.
* tests: slightly bigger raid arraysZdenek Kabelac2016-09-131-8/+7
| | | | Just to ensure we catch devices in sync.
* tests: more permissive on test percent valueZdenek Kabelac2016-09-131-4/+5
| | | | | Just check there is some output. Values may slightly differ per policy target version.
* tests: use just single raid_leg_statusZdenek Kabelac2016-09-134-39/+35
| | | | Simplify 'check' test actualy and correct printed tracing output
* tests: not redirect strderr to stdoutZdenek Kabelac2016-09-131-2/+5
| | | | Errors are 'wanted' and expected in this case.
* libdm: cleaner debug messageZdenek Kabelac2016-09-131-1/+1
|
* rpm: install lvmreport.7Zdenek Kabelac2016-09-121-0/+1
|
* tests: slow down disks moreZdenek Kabelac2016-09-121-1/+1
|
* tests: add check function for raid leg statusZdenek Kabelac2016-09-125-43/+49
| | | | | | | 2 new check test functions: raid_leg_status - to just compare raid_leg_status_is - to compare and die when different
* tests: use exclusive activationZdenek Kabelac2016-09-121-2/+2
| | | | | Slightly better for clvmd - thought test is still crashing as table is broken.
* tests: move cache test to separate fileZdenek Kabelac2016-09-122-11/+43
| | | | Don't mix plain raid test with 'raid+cache' test.
* activation: dso always defined for monitoring queryZdenek Kabelac2016-09-122-2/+3
| | | | | Ensure 'dso' has always a defined (NULL) value, and also ensure NULL 'dso' is not dereferenced.
* man: add lvmreport man pagePeter Rajnoha2016-09-123-1/+1812
|
* man: Only install lvmraid when needed.Alasdair G Kergon2016-09-122-3/+9
|
* cache: fixed copy&paste from last commitZdenek Kabelac2016-09-091-1/+1
|
* rpm: build with raid man pageZdenek Kabelac2016-09-091-0/+1
|
* tests: rename test _ -> -Zdenek Kabelac2016-09-091-0/+0
| | | | Change '_' in the test name.
* tests: increate delay for raid rebuildZdenek Kabelac2016-09-092-3/+3
| | | | | | Delay writes just to usable extents on a PV (so lvm2 metadata update remains fast). Raise delay to 10ms for write.
* tests: skip synaction test in cluster for nowZdenek Kabelac2016-09-091-0/+6
| | | | Until we resolve it - we do not support syncaction on clustered VG.
* tests: lowering disc usageZdenek Kabelac2016-09-091-33/+26
| | | | | | | | | | | | | | | Correction for aux test result ([] -> if;then;fi) Use issue_discard to lower memory demands on discardable test devices Use large devices directly through prepare_pvs I'm still observing more then 0.5G of data usage through. Particullary: 'lvcreate' followed by 'lvconvert' (which doesn't yet support --nosync option) is quite demanging, and resume returns quite 'late' when a lot of data has been already written on PV.
* cache: fix reporting of dirty cacheZdenek Kabelac2016-09-094-7/+10
| | | | | When cache has zero used blocks it's been wrongly reported as 100.00% dirty. Fix it and report 0.00.
* lvm2app: fix cache percantage reportingZdenek Kabelac2016-09-092-2/+3
| | | | | In lvm2app we were always returning dirty (copy%) value. Return properly data & metadata usage values.
* cache: report metadata percentageZdenek Kabelac2016-09-095-1/+32
| | | | | | | Reinstantiate reporting of metadata percent usage for cache volumes. Also show the same percentage with hidden cache-pool LV. This regression was caused by optimization for a single-ioctl in 2.02.155.
* tests: lower allocated memoryZdenek Kabelac2016-09-071-1/+1
| | | | | Use smaller mirror to have faster sync. TODO: switch to delayed devs...
* cleanup: clean gcc6 minor/major types warningsZdenek Kabelac2016-09-072-0/+2
| | | | | Put sys/sysmacros.h in front of sys/types.h header file as requested by gcc6 part II.
* cache: scrubbing for cache origin LV - Bug 1169495Brassow Jonathan2016-09-073-1/+40
| | | | | | | | | | | | | | | | | | Allow RAID scrubbing on cache origin sub-LV This patch adds the ability to perform RAID scrubbing on the cache origin sub-LV (https://bugzilla.redhat.com/1169495). Cache origin operations are restricted to non-clustered RAID LVs until there can be further testing in a cluster (even for exclusive activation). User can either specify directly _corig LV or he can specify cache LV and operation --syncation is passed ONLY to _corig LV. If users wants to manipulation with cache-pool devices - he needs to specify this object name. Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
* post-releaseAlasdair G Kergon2016-09-074-2/+8
|
* pre-releasev2_02_165Alasdair G Kergon2016-09-074-6/+11
|
* man: Additional info on exit statuses.Alasdair G Kergon2016-09-071-0/+5
|
* man lvmraid: installDavid Teigland2016-09-061-1/+1
|
* man lvmraid: comment out unfinished featuresDavid Teigland2016-09-061-16/+26
|
* man lvmraid: remove rebuild exampleDavid Teigland2016-09-061-5/+0
|
* man: add lvmraid(7)David Teigland2016-09-061-0/+1314
|
* dev-type: check for DEVLINKS udev db variable existence if ↵Peter Rajnoha2016-09-062-0/+8
| | | | | | | | | | | | | | | | udev_device_get_is_initialized fn is not present Older udev versions (udev < v165), don't have the official udev_device_get_is_initialized function available to query for device initialization state in udev database. Also, devices don't have USEC_INITIALIZED udev db variable set - this is bound to the udev_device_get_is_initialized fn functionality. In this case, check for "DEVLINKS" variable instead - all block devices have at least one symlink set for the node (the "/dev/block/<major:minor>". This symlink is set by default basic udev rules provided by udev directly. We'll use this as an alternative for the check that initial udev processing for a device has already finished.
* lvmetad: Unused includes.Alasdair G Kergon2016-09-051-4/+0
|
* dev-type: use more appropriate messages in udev_dev_is_mpath_component and ↵Peter Rajnoha2016-09-051-16/+42
| | | | use 10s timeout
* refactor: move and rename _dev_is_mpath_component in lvmetad.c to ↵dev-dct-pvscan-multipathPeter Rajnoha2016-09-054-63/+69
| | | | udev_dev_is_mpath_component in dev-type.c
* lvmetad: check udev for mpath component several times if udev record not ↵Peter Rajnoha2016-09-051-6/+26
| | | | | | | | | | | | initialized yet It's possible (mainly during boot) that udev has not finished processing the device and hence the udev database record for that device is still marked as uninitialized when we're trying to look at it as part of multipath component check in pvscan --cache code. So check several times with a short delay to wait for the udev db record to be initialized before giving up completely.
* lvmetad: use udev to ignore multipath components during scanDavid Teigland2016-08-311-0/+51
| | | | | | | | | | | | | | | | | | | | | When scanning devs to populate lvmetad during system startup, filter-mpath with native sysfs multipath component detection may not detect that a dev is multipath component. This is because the multipath devices may not be set up yet. Because of this, pvscan will scan multipath components during startup, will see them as duplicate PVs, and will disable lvmetad. This will leave lvmetad disabled on systems using multipath, unless something or someone runs pvscan --cache to rescan. To avoid this problem, the code that is scanning devices to populate lvmetad will now check the udev db to see if a dev is a multipath component that should be skipped. (This may not be perfect due to inherent udev races, but will cover most cases and will be at least as good as it's ever been.)
* tests: skip test for older cache targetZdenek Kabelac2016-08-311-5/+11
| | | | | | Some test on older can targets are not going to work, and since there is no other fix then using newer kernel - skip such tests completely.
* dmeventd: typo and debug name fixZdenek Kabelac2016-08-311-5/+5
| | | | | Fix 'raw' -> 'row' fix. Consitently use thin pool as a type of monitored device in info message.
* lvmdump: use lsblk -s and lsblk -O in lvmdump only if these options are ↵Peter Rajnoha2016-08-302-3/+11
| | | | | | | | | | | supported The lsblk is just a nice helper here - it's not crucial for lvmdump so do best effort here and use the most we can from current version of lsblk that is installed on system. The lsblk -s option was added a bit later after lsblk introduction and lsblk -O support even more later - so if these are not available, use only pure lsblk output without any extras.
* config: regenerateAlasdair G Kergon2016-08-301-2/+8
|
* raid10: Fix #stripes in lvcreate msg when too many.Alasdair G Kergon2016-08-302-1/+2
|
* lvmdbusd: Prefix tag string with '@'Tony Asleson2016-08-291-4/+1
|
* lvmdbustest.py: Add tag regression testTony Asleson2016-08-291-5/+18
| | | | Add '-' back in as acceptable tag character
* lvmdbusd: WS/pep8 correctionsTony Asleson2016-08-297-28/+33
|
* lvmdbusd/lvmdb.py: Make stand alone execution workTony Asleson2016-08-292-6/+6
| | | | This was broken when the args were moved to cfg
* lvmdbusd: Correct importsTony Asleson2016-08-295-23/+9
|
View Lorry Controller Status