summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* tests: integrity-caching: ensure raid redundancyHEADmastermainDavid Teigland2023-05-172-8/+20
| | | | | | | The recent fix 05c2b10c5d0a9 ensures that raid LV images are not using the same devices. This was happening in the lvextend commands used by this test, so fix the test to use more devices to ensue redundancy.
* tests: integrity: snapshots now work on raid+integrityDavid Teigland2023-05-171-8/+0
|
* toollib: provide proper hint for referencing VG uuid in case of duplicate VG ↵Peter Rajnoha2023-05-163-1/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | names vgrename does not support -S|--select, so do not provide a hint about using it. Instead, provide a hint about using VG uuid directly. ❯ vgs WARNING: VG name vg1 is used by VGs DXjcSK-gWfu-5gLh-9Kbg-sG49-dtRr-GqXzGL and MVMfyM-sjOa-M2xV-AT4Y-JddR-h4SP-UO5Ttk. Fix duplicate VG names with vgrename uuid, a device filter, or system IDs. VG #PV #LV #SN Attr VSize VFree vg1 1 0 0 wz--n- 124.00m 124.00m vg1 1 0 0 wz--n- 124.00m 124.00m (vgrename does not support -S|--select) ❯ vgrename vg1 vg2 WARNING: VG name vg1 is used by VGs DXjcSK-gWfu-5gLh-9Kbg-sG49-dtRr-GqXzGL and MVMfyM-sjOa-M2xV-AT4Y-JddR-h4SP-UO5Ttk. Fix duplicate VG names with vgrename uuid, a device filter, or system IDs. Multiple VGs found with the same name: skipping vg1 Use VG uuid in place of the VG name. (vgchange does support -S|--select) ❯ vgchange --addtag a vg1 WARNING: VG name vg1 is used by VGs DXjcSK-gWfu-5gLh-9Kbg-sG49-dtRr-GqXzGL and MVMfyM-sjOa-M2xV-AT4Y-JddR-h4SP-UO5Ttk. Fix duplicate VG names with vgrename uuid, a device filter, or system IDs. Multiple VGs found with the same name: skipping vg1 Use --select vg_uuid=<uuid> in place of the VG name.
* raidintegrity: allow snapshotsDavid Teigland2023-05-114-8/+446
|
* Fix "multisegment RAID1, allocator uses one disk for both legs"heinzm2023-05-101-0/+41
| | | | | | | | In case of e.g. 3 PVs, creating or extending a RaidLV causes SubLV collocation thus putting segments of diffent rimage (and potentially larger rmeta) SubLVs onto the same PV. For redundant RaidLVs this'll compromise redundancy. Fix by detecting such bogus allocation on lvcreate/lvextend and reject the request.
* tests: more updates for 300M xfsZdenek Kabelac2023-05-101-8/+9
| | | | | Fix some sizing for larger xfs testing. Also fix resize of reiserfs which requires resize_fsadm.
* tests: skip this testing without newer blkidZdenek Kabelac2023-05-101-0/+5
| | | | Testing xfs --fs functionality needs new blkid.
* cov: hide some false positivesZdenek Kabelac2023-05-106-3/+5
| | | | | | Hide some false positives. Note: there must not a be blank line after coverity hiding comment.
* cov: remove unneeded header file inclusionZdenek Kabelac2023-05-102-2/+0
|
* cov: validate dev_get_primary_dev resultZdenek Kabelac2023-05-101-1/+2
| | | | Make sure primary_dev is defined when using it.
* tests: needs to be exported for tracingZdenek Kabelac2023-05-061-1/+1
|
* tests: adapt for xfs 300M min sizeZdenek Kabelac2023-05-062-39/+34
| | | | Some test still were missed to be converted for XFS 300M min size.
* tests: different check for mounted volumeZdenek Kabelac2023-05-061-1/+1
| | | | | It appears newer mount allows repeated mounting ?? Anyway - do the check with grep.
* tests: check for lvmdbusd running in the systemZdenek Kabelac2023-05-061-0/+5
| | | | | | Check for running (possibly leftover) lvmdbusd running in the system - as this daemon may interfere with this test as in this case both be operating on same 'live' data in /run/lvm.
* tests: update lvextend testsZdenek Kabelac2023-05-062-895/+560
| | | | | | | | Make test faster by agregating sets of operation to work on a single created filesystem yet checking all the variants of extension and reduction. Split 'xfs' part into separate test and convert it for use of the minimal size 300M nowdays required by mkfs.xfs.
* aux: retry brd removalZdenek Kabelac2023-05-061-9/+14
| | | | | | Try to remove brd twice if there is some collision with udevd. Instanciate only 1 ramdisk. Use just 'eval' for '--nameprefixes' results.
* aux: wipefs_a takes list of devicesZdenek Kabelac2023-05-061-24/+24
| | | | | | | Enhance function to take list of device so set of devices can be wiped with a single call: aux wipefs_a "$dev1" "$dev2"
* vdo: document feature optionZdenek Kabelac2023-05-062-4/+4
|
* cov: check syscall resultZdenek Kabelac2023-05-061-1/+2
|
* cov: remove unused but set variablesZdenek Kabelac2023-05-066-17/+13
|
* cleanup: correcting some log_printZdenek Kabelac2023-05-0614-91/+92
| | | | | Correcting to log_print_unless_silent(), so -qq can do some work.
* cov: some initializersZdenek Kabelac2023-05-062-6/+6
|
* cov: hide problem with 64bit time_tZdenek Kabelac2023-05-061-1/+1
|
* cov: validata top_lvZdenek Kabelac2023-05-061-0/+5
| | | | Add explicit pointer check is never NULL.
* cov: ensure there is either vg or error_vgZdenek Kabelac2023-05-061-2/+3
| | | | | Make it explicitely visible to coverity that _process_pvs_in_vg() is not passing NULL vg.
* cov: ensure NULL baton is not dereferencedZdenek Kabelac2023-05-061-1/+1
|
* cov: simplier codeZdenek Kabelac2023-05-061-14/+21
| | | | | Avoid coverity to contruct some abstract scenarions of 'cft' modification and simplify the code at the same time.
* Fix "lvconvert -m 0 will always take rimage_0 even if it is out-of-sync"heinzm2023-05-051-2/+11
| | | | | | Bail out in case first rimage is out-of-sync. Refresh first, i.e. "lvchange --resync $RaidLV", then retry downgrade to linear after resynchronization.
* lvreduce: make _lvseg_get_stripes handle integrity layerDavid Teigland2023-05-031-9/+26
| | | | | | | lvreduce uses _lvseg_get_stripes() which was unable to get raid stripe info with an integrity layer present. This caused lvreduce on a raid+integrity LV to fail prematurely when checking stripe parameters. An unhelpful error message about stripe size would be printed.
* pvck: improve error for write to existing fileDavid Teigland2023-04-281-0/+5
|
* lvmcache: fix valgrind error when dropping md duplicateDavid Teigland2023-04-251-0/+7
| | | | | | | When lvmcache info is dropped because it's an md component, then the lvmcache vginfo can also be dropped, but the list iterator was still using the list head in vginfo, so break from the loop earlier to avoid it.
* tests: adapt waiting for pvmove startZdenek Kabelac2023-04-253-9/+4
| | | | | | Previous commit cause the pvmove could actually be started in unexpected order - so make sure, we are not starting new pvmove in same VG until the previous one is started.
* tests: utils now print also df_hZdenek Kabelac2023-04-251-4/+8
| | | | | | Add info about space usage on devices after the test. Add some more skipped dirs.
* tests: some aux correctionsZdenek Kabelac2023-04-251-6/+7
| | | | | | | Keep backups within test_dir instead of dev_dir (so it doesn't leak large files there if the tests are run over real /dev dir). Move restoring of dm_mirror throttling before test_dir is removed.
* tests: fix pattern for raid4Zdenek Kabelac2023-04-253-3/+3
| | | | | Since the strip in raid4 might be XOR - we might eventually end with 2 blocks of 'B' on 2 disks - so will rest of stripe with 'b'.
* tests: use 300M lv size for xfsZdenek Kabelac2023-04-251-1/+1
|
* tests: try to retry remove of scsi_debugZdenek Kabelac2023-04-251-1/+6
| | | | | | Not quite sure if this helps anything, some of testing machines can't reliably remove scsi_debug, reporting they are in use - but it's not easily reproducible...
* tests: handle multiple devs with wait_pvmove_lv_readyZdenek Kabelac2023-04-253-31/+27
| | | | | | | | | aux wait_pvmove_lv_ready() now handles multiple pvmove LVs at one go - which allows a bit fast checking - although at some point we may need to switch to use delayed devs since mirror throttling seems to be no longer working well, as CPU are getting so fast, that most of data are already pvmoved before throttling has any chance to do something...
* tests: skip some unneeded testZdenek Kabelac2023-04-2517-4/+25
| | | | Skip irelevant tests for polld & lockd pass.
* aux: use unused brd device for testingZdenek Kabelac2023-04-251-0/+3
| | | | | | | | | | | When 'brd' device can be removed (is unused AKA not opened), remove such device and use again for testing. Let's assume user has no unused brd device left in the system. When the 'tests' sometimes fail to cleanup devices, with this change futher cleanup from some next test may evenually release brd device and make it available for testing.
* aux: more efficient lvmlock shutdownZdenek Kabelac2023-04-251-6/+2
|
* wipe_lv: use zeroing ioctl only for large sizesZdenek Kabelac2023-04-251-1/+1
| | | | | | | | | | | | There is no easy way to detect, whether device supports zeroing, and kernel also zeroes device when it's not directly supported, but with extra message: operation not supported error, dev X, sector Y op 0x9:(WRITE_ZEROES)... So to avoid generating such message with every 'lvcreate', use for zeroing of upto 8K just standard write of zeroed page. (maybe we can go with even larger sizes).
* fix dev_name use in add_areas_lineDavid Teigland2023-04-241-16/+29
| | | | | This function was relying on dev_name() returning NULL to indicate no device, but dev_name never returns NULL.
* lvmdbus: preserve PATH envvarZdenek Kabelac2023-04-231-0/+2
|
* tests: enforce 4K block for integrity fsZdenek Kabelac2023-04-232-4/+4
| | | | | | With raid tests it's important we don't get spread of 4K file across 1K block on a multiple disk stripe - so use 4K block size for ext4 fs.
* aux: loop doesn't support zeroing discardZdenek Kabelac2023-04-231-0/+1
| | | | | To avoid logging unsupported WRITE_ZEROES with loop, disable usage for this backend device.
* tests: hide some more file in error traceZdenek Kabelac2023-04-221-1/+2
| | | | Hide unneeded dev nodes.
* makefiles: forgotten to install some test configZdenek Kabelac2023-04-221-1/+1
| | | | rpm testing missed config files.
* test: use aux wait_recalcZdenek Kabelac2023-04-221-46/+15
| | | | Use aux function.
* test: convert to use ext4Zdenek Kabelac2023-04-222-54/+51
| | | | Modify test to check same properties with less demanding ext4.
View Lorry Controller Status