summaryrefslogtreecommitdiff
path: root/test/shell
Commit message (Collapse)AuthorAgeFilesLines
* 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: handle multiple devs with wait_pvmove_lv_readyZdenek Kabelac2023-04-252-5/+2
| | | | | | | | | 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.
* 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.
* 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.
* tests: add data syncZdenek Kabelac2023-04-211-0/+2
|
* aux: add wait_recalcZdenek Kabelac2023-04-217-462/+243
| | | | Share function across tests.
* tests: convert to use ext4Zdenek Kabelac2023-04-213-61/+35
| | | | | | | | | | | Convert test to use only ext4 instead of 300M demanding XFS. Shorten 'B' files to 4K and use 4K strip size with >raid1 arrays so we do not risk spreading of the file across stripe. Also use easier 'aux corrupt_dev()' method to introduce a bit corruption into a block device with integrity. TODO: shorten _wait_recalc (should't be needed).
* tests: use aux clear_devZdenek Kabelac2023-04-216-36/+11
| | | | Use wrapper over 'blkdiscard -z'
* cache: fix snapshot of cache with cachevolDavid Teigland2023-04-101-0/+162
| | | | | Creating a snapshot of a cache LV with a cachevol would fail because cache_check was not being skipped.
* tests: use less demanding ext4Zdenek Kabelac2023-04-061-2/+2
|
* tests: lower demand for disk resourcesZdenek Kabelac2023-04-064-448/+97
| | | | | | | | Convert test to use a single skeleton and only different pieces keep in separate tests. Lower raid disk usage to smaller size and switch to ext4 as way less demanding fileystem.
* raidintegrity: allow writecache and cacheDavid Teigland2023-04-051-0/+561
| | | | Allow writecache|cache over raid+integrity LV.
* tests: integrity fixesDavid Teigland2023-04-051-19/+37
| | | | | wait_recalc was mistakenly being called on raid without integrity wait_recalc loop was exiting without error
* tests: nomda-restoremissingDavid Teigland2023-03-201-1/+12
| | | | | | This test was broken by commit 69ea2e3f9 "vg_read: keep MISSING_PV when device with no mda reappears" Change the test to match the new behavior.
* tests: update missing-pvDavid Teigland2023-03-081-34/+72
| | | | add more checks and expand comments explaining behavior
* tests: vg-raid-takeoverDavid Teigland2023-03-084-0/+707
| | | | | | Different sequences of steps that could be used to handle raid LVs after VG takeover (what would happen in cluster failover) combined with the loss of a disk.
* vgchange: allow changing system ID with majority of PVsDavid Teigland2023-03-081-1/+68
| | | | | | when used with --majoritypvs. This allows the fail-over of a VG between systems by changing the VG system ID when a PV is missing.
* lvresize: fix check for mounted and renamed LV to handle spacesDavid Teigland2023-02-231-0/+14
| | | | | | | | | | Replace spaces with \040 in directory paths from getmntent (mtab). The recent commit 5374a44c5712 compares mount point directory paths from /etc/mtab and /proc/mounts, in order to detect when a mounted LV has been renamed. The directory path comparison does not work correctly when the path contains spaces because getmntent uses ascii space chars and proc replaces spaces with \040.
* tests: add missing quotesZdenek Kabelac2023-02-231-34/+40
| | | | | | Add quotes around paths and also add fixme for checking system is actually usable for a test with all running services.
* tests: use aux mdadm wrapperZdenek Kabelac2023-02-232-9/+7
| | | | | Wrapper takes care of proper MD device name around its various incarnations.
* tests: remove option chunk for mdadm raid1Zdenek Kabelac2023-02-232-3/+8
| | | | | Not sure why, but --chunk specification for mdadm raid1 is no longer 'wanted' ???
* tests: add fixmeZdenek Kabelac2023-02-231-1/+2
|
* tests: some skips with 6.2 kernelZdenek Kabelac2023-02-232-0/+8
| | | | Fix did not managed to get to final release so skip test on this kernel.
* tests: safety first...Zdenek Kabelac2023-02-171-0/+4
|
* tests: check failing vdo conversionZdenek Kabelac2023-02-171-2/+8
| | | | When we detect not usable vdo on a machine, check lvconvert fails.
* tests: skip test without mkfs.ext4Zdenek Kabelac2023-02-131-0/+2
|
* tests: reduce shellcheck warnsZdenek Kabelac2023-02-1025-86/+82
| | | | Reduce warnings in tests.
* tests: remove blank lineZdenek Kabelac2023-02-101-1/+0
|
* vgimportclone: fix non-duplicate PV with non-unique basevgname argDavid Teigland2023-02-091-0/+20
| | | | | | | | | | | | | | | | Fix hang of vgimportclone command when: the PV(s) being imported are not actually clones/duplicates, and the -n vgname arg is the same as the current vgname. (Not the intended use of the command, but it should still work.) In this case, the old and new vgnames ended up being the same, when the code expected they would be different. A file lock on both the old and new vgnames is used, so when both flocks are on the same file, the second blocks indefinitely. Fix the new vgname to be the old name plus a numeric suffix, which is the expected result.
* device_id: ignore quotes in device idDavid Teigland2023-02-061-0/+24
| | | | | | A t10 wwid string was found containing a " character which breaks vg metadata parsing. Ignore any quotation marks in device id strings.
* lvresize: fail early if mounted LV was renamedDavid Teigland2023-01-261-0/+11
| | | | | | If a mounted LV is renamed, then fs resizing utilities will fail, so detect this condition and fail the command before any changes are made.
* lvresize: only resize crypt when fs resize is enabledDavid Teigland2023-01-191-1/+6
| | | | | | | | | | | There were a couple of cases where lvresize, without --fs resize, was resizing the crypt layer above the LV. Resizing the crypt layer should only be done when fs resizing is enabled (even if the fs is already small enough due to being independently reduced.) Also, check the size of the crypt device to see if it's already been reduced independently, and skip the cryptsetup resize if it's not needed.
* tests: vdo resizingZdenek Kabelac2023-01-161-0/+15
|
* tests: vgimportclone with incomplete pv list and nomda pvDavid Teigland2023-01-051-1/+20
|
* tests: lvresize-fs-crypt using helper only for crypt devDavid Teigland2023-01-031-0/+25
|
* device_id: fix segfault verifying serial for non-pvDavid Teigland2022-12-021-0/+79
| | | | | | | The recent change that verifies sys_serial system.devices entries using the PVID did not exclude non-PV devices from being checked. The verification code would attempt to use du->pvid which was null for the non-PVs causing a segfault.
* tests: devicesfile-vpd-ids add nvme wwidDavid Teigland2022-11-211-3/+28
|
* tests: update test to handle different statusZdenek Kabelac2022-11-081-3/+4
| | | | | | | Since now we change deduplication with V4 table line change, the modification tends to be faster and we can capture for a few ms also 'status' about opening or closing deduplication index. Use 'grep -E' to handle both words.
* device_id: handle duplicate serial numbersDavid Teigland2022-11-071-0/+777
| | | | | | | | | Handle multiple devices using the same serial number as their device id. After matching devices to devices file entries, if there is a discrepency between the ondisk PVID and the devices file PVID, then rematch devices to devices file entries using PVID, looking at all disks on the system with the same serial number.
* lvreduce: require active LV when no fs option is usedDavid Teigland2022-10-111-3/+4
| | | | | Without an --fs option set, make lvreduce of an inactive LV fail and report that the LV must be active.
* tests: add comments to fsadm-renamedDavid Teigland2022-10-111-0/+15
| | | | | to explain the what and why of the steps that are not obvious
* tests: skip lvresize tests without mkfs.xfsDavid Teigland2022-10-102-0/+4
|
* tests: device ids using vpd dataDavid Teigland2022-10-101-0/+201
|
* tests: discard updateZdenek Kabelac2022-09-211-2/+6
|
* tests: integrity switch to ext4Zdenek Kabelac2022-09-213-18/+14
| | | | | Since we would need to create a lot of 300M filesystem, switch this test suite to ext4.
* vgremove: remove online files in run dirDavid Teigland2022-09-141-2/+37
| | | | | | | | | | | These files are automatically cleared on reboot given that /run is tmpfs, and that remains the primary way of clearing online files. But, if there's extreme use of vgcreate+pvscan+vgremove between reboots, then removing online files in vgremove will limit the number of unused online files using space in /run.
* tests: skip new lvresize tests when missing new libblkidDavid Teigland2022-09-133-0/+20
|
View Lorry Controller Status