| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
Fix some sizing for larger xfs testing.
Also fix resize of reiserfs which requires resize_fsadm.
|
|
|
|
| |
Testing xfs --fs functionality needs new blkid.
|
| |
|
|
|
|
| |
Some test still were missed to be converted for XFS 300M min size.
|
|
|
|
|
| |
It appears newer mount allows repeated mounting ??
Anyway - do the check with grep.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Try to remove brd twice if there is some collision with udevd.
Instanciate only 1 ramdisk.
Use just 'eval' for '--nameprefixes' results.
|
|
|
|
|
|
|
| |
Enhance function to take list of device so set of devices
can be wiped with a single call:
aux wipefs_a "$dev1" "$dev2"
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Add info about space usage on devices after the test.
Add some more skipped dirs.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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'.
|
| |
|
|
|
|
|
|
| |
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...
|
|
|
|
|
|
|
|
|
| |
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...
|
|
|
|
| |
Skip irelevant tests for polld & lockd pass.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
To avoid logging unsupported WRITE_ZEROES with loop,
disable usage for this backend device.
|
|
|
|
| |
Hide unneeded dev nodes.
|
|
|
|
| |
rpm testing missed config files.
|
|
|
|
| |
Use aux function.
|
|
|
|
| |
Modify test to check same properties with less demanding ext4.
|
|
|
|
|
| |
Actually oseek comes only with rawhide's version,
just use the standard option name.
|
| |
|
|
|
|
| |
Share function across tests.
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
| |
Use wrapper over 'blkdiscard -z'
|
|
|
|
|
|
|
| |
Add function to corrupt some bytes in give file path presenting
a device. 1st. patern in just once replaced with 2nd. pattern.
Usable to simulate some bit corruption for integrity devices.
|
|
|
|
|
| |
Function that will use 'blkdiscard -z' and fallbacks
to 'dd' when such option is not available.
|
| |
|
|
|
|
|
| |
Creating a snapshot of a cache LV with a cachevol would fail
because cache_check was not being skipped.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Allow writecache|cache over raid+integrity LV.
|
|
|
|
|
| |
wait_recalc was mistakenly being called on raid without integrity
wait_recalc loop was exiting without error
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Signed-off-by: Tony Asleson <tasleson@redhat.com>
|
|
|
|
|
| |
Not doing this by default for automated build testing as it generates a
lot of output and slows things down by another ~10%.
|
|
|
|
|
| |
This is currently need if we are collecting code coverage data as we don't
handle this unit test correctly.
|
| |
|
| |
|
|
|
|
|
| |
Make the error injection wrapper handle the exit case, so that we can
clean up gracefully when instructed to do so.
|
|
|
|
|
|
| |
Previously we were injecting a missing key in the lv, vg, and pv.
Given the order of processing in lvmdbusd, this prevented us from
exercising all the error paths. Change to returning just 1 instead.
|
| |
|