summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAge
* tests: handle change to DDF assembly.NeilBrown2014-05-21
| | | | | | | | | | When a DDF array is assembled with missing devices, those devices are now alway marked as 'missing' and cannot just re-appear in the array and be working again. test must be changed to acknowledge this. Signed-off-by: NeilBrown <neilb@suse.de>
* tests: handle new raid10/ddf geometries.NeilBrown2014-05-21
| | | | | | | Recent changes to support more ddf geometries using raid1e requires updates to tests. Signed-off-by: NeilBrown <neilb@suse.de>
* ddf-sudden-degraded test fix.NeilBrown2014-03-26
| | | | | | | Change how sudden-degraded devices should appear. We don't record failure, we record that the device isn't there. Signed-off-by: NeilBrown <neilb@suse.de>
* tests: add test that DDF marks missing devices as failed on assembly.NeilBrown2014-03-11
| | | | | | | If we assemble a newly-degraded array, the missing devices must be marked as 'failed' so we don't expect them in future. Signed-off-by: NeilBrown <neilb@suse.de>
* New test: 03r5assem-failedNeilBrown2014-02-25
| | | | | | | This test currently fails, confirming a bug which was recently reported. Signed-off-by: NeilBrown <neilb@suse.de>
* ddf tests: fix get_rootdevNeilBrown2013-11-19
| | | | | | | Getting the major number from the hex device number should take all-but-the-last-two digits, rather than just the first two digits. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-incremental-wrong-order: new unit testmwilck@arcor.de2013-10-16
| | | | | | | | | | | | | This is a test simulating two temporary missing disks. These will have less recent meta data than the other disks in the container. When the array is reassembled, we expect mdadm to detect that and react to it by using the meta data of the more recent disks as reference. This test FAILS with mdadm 3.3 for DDF. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-assemble-missing: new unit testmwilck@arcor.de2013-10-16
| | | | | | | | | | | This is a test case for handling incremental assembly correctly after disks had been missing once. This test is the basis for other similar but more tricky test cases involving inconsitent meta data. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/env-ddf-template: add helper function for checksumsmwilck@arcor.de2013-10-16
| | | | | Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-readd-readonly: new unit test.mwilck@arcor.de2013-10-16
| | | | | | | | A test for my recent patch "Monitor: write meta data in readonly state, sometimes". Test that a faulty disk is recorded in the meta data. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/env-ddf-template: fix container namemwilck@arcor.de2013-10-16
| | | | | | | /dev/md/ddf0 works also with assembly. /dev/md/ddf doesn't. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-stop-readd: New DDF unit testmwilck@arcor.de2013-10-16
| | | | | | | | This is similar to 10ddf-fail-readd. The difference is that the array is stopped and incrementally assembled before the disk is re-added. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-readd: New DDF unit testmwilck@arcor.de2013-10-16
| | | | | | This unit test is for a simple fail/remove/readd scenario. Signed-off-by: NeilBrown <neilb@suse.de>
* DDF test: make sure mdmon isn't started by systemdmwilck@arcor.de2013-10-16
| | | | | | | For testing we usually want the locally built mdmon, not the one systemd prefers. Signed-off-by: NeilBrown <neilb@suse.de>
* DDF tests: allow to run on systems without /dev/sdamwilck@arcor.de2013-10-16
| | | | | | | Some ddf tests scripts assume that /dev/sda is always present. That's wrong e.g. on VMs. Use a more general approach. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-create-race: test handling of fail/create racemwilck@arcor.de2013-08-08
| | | | | | | | | If a disk fails and simulaneously a new array is created, a race condition may arise because the meta data on disk doesn't reflect the disk failure yet. This is a test for that case. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-spare: more sophisticated result checksmwilck@arcor.de2013-08-08
| | | | | | | This test can succeed two ways, depending on timing. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-two-spares: new unit testmwilck@arcor.de2013-08-08
| | | | | | | This is one more unit test for failure/recovery, this time with double redundancy, which isn't covered by the other tests. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-spare: new unit testmwilck@arcor.de2013-08-06
| | | | | | | This is Albert Pauw's latest test. Note that this FAILS. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-twice: remove hard-coded assumptionsmwilck@arcor.de2013-08-06
| | | | | | | | | This test has some randomness because it is not always deterministic which of the two arrays gets the spare and which remains degraded. Handle it. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/env-ddf-template: some helper functionsmwilck@arcor.de2013-08-06
| | | | | | | | helper functions to determine the list of devices in an array, etc. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-fail-twice: New unit testmwilck@arcor.de2013-08-05
| | | | | | | This is the test by Albert Pauw. Fail 2 disks, and add one. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/env-ddf-template: helper for new unit testMartin Wilck2013-07-31
| | | | | | | | I forgot to check in this helper script, similar to the one for IMSM. It is needed by tests/10ddf-create-fail-rebuild. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-create-fail-rebuild: new unit test for DDFMartin Wilck2013-07-31
| | | | | | | | This test adds a new unit test similar to 009imsm-create-fail-rebuild. With the previous patches, it actually succeeds on my system. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* Add test for --replace handling.NeilBrown2013-07-24
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* Improve revert testsNeilBrown2013-07-24
| | | | | | | 1/ perform revert-grow on more metadata versions 2/ add revert-inplace. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-geometry: new unit testmwilck@arcor.de2013-07-22
| | | | | | Test various RAID geometries, creation and deletion of subarrays Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-create: create RAID5 firstmwilck@arcor.de2013-07-22
| | | | | | | | Let the first created array be RAID5 rather than RAID0. This makes the test harder than before, because everything after the first Create has do be done indirectly through mdmon. Signed-off-by: NeilBrown <neilb@suse.de>
* test/10-ddf-create: fix commentsmwilck@arcor.de2013-07-09
| | | | | | Comments should reflect the changes in the script. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-create: add RAID 10 arraymwilck@arcor.de2013-07-08
| | | | | | | | This patch adds RAID10 support to the DDF test script. It actually passes! Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* tests: add test to revert shrinking reshapes.NeilBrown2013-07-04
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* tests: add a test for reverting reshapesNeilBrown2013-07-04
| | | | | | Only reverting reshapes that grow the array so far. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/raid6repair: default data offset has changed.NeilBrown2013-06-27
| | | | | | So the test scripts must change too. Signed-off-by: NeilBrown <neilb2suse.de>
* tests: add device size tests when change raid leve to/from 0NeilBrown2013-06-25
| | | | | | There was a kernel bug that got this wrong, so better check for it. Signed-off-by: NeilBrown <neilb@suse.de>
* tests: add test for converting levels to raid0 and back.NeilBrown2013-06-24
| | | | | | | Now that I have this mostly working, I should make sure it doesn't break... Signed-off-by: NeilBrown <neilb@suse.de>
* test/00names: use appropriate mdadm.confNeilBrown2013-06-24
| | | | | | | Using non-numeric names needs an mdadm.conf setting, so make sure we have one. Signed-off-by: NeilBrown <neilb@suse.de>
* tests: add test for non-numeric device namesNeilBrown2013-06-19
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* Add test for interaction of --assemble with --incrNeilBrown2013-06-19
| | | | | | | and fix the bug that it found. The refactor of start_array() missed a test. Signed-off-by: NeilBrown <neilb@suse.de>
* Add test for --update=metadata and fix bug it found.NeilBrown2013-06-19
| | | | | | We were not setting device size correctly for raid0. Signed-off-by: NeilBrown <neilb@suse.de>
* tests: rearrange sometest groupings.NeilBrown2013-06-19
| | | | | | | All 'update' tests in 04 More imsm tests in 09 Signed-off-by: NeilBrown <neilb@suse.de>
* Remove lots of unnecessary white space.NeilBrown2013-06-19
| | | | | | | Now that I am using white-space mode in Emacs I can see all of this, and I don't like it :-) Signed-off-by: NeilBrown <neilb@suse.de>
* tests: zero devices before --adding them.NeilBrown2013-05-01
| | | | | | | | Linux 3.10 will allow more "--add" to be handled as "--re-add". To be sure the tests work correctly we sometimes need to zero the device to ensure it really is an --add that happens. Signed-off-by: NeilBrown <neilb@suse.de>
* tests/10ddf-create: omit log output checkmwilck@arcor.de2013-04-23
| | | | | | | | | The test script was counting output lines - its expectations don't match the current code any more. Remove this pointless test. Signed-off-by: Martin Wilck <mwilck@arcor.de> Signed-off-by: NeilBrown <neilb@suse.de>
* test: add --disable-integrity switch.NeilBrown2012-11-20
| | | | | | | The integrity tests are very slow and aren't always needed. So make them optional. Signed-off-by: NeilBrown <neilb@suse.de>
* Tests: adjust for recent changes.NeilBrown2012-11-20
| | | | | | | | | | | | commit cb19a251a581fe78dcddd1d95dca4d8cb7664819 super1: reserve at least 2 chunks for reshape headroom. reserved more space in a RAID5, so we need to update to array sizes when reshaping. Also make sure reshape tests we change the shape: raid5->raid1 was failing and we didn't notice. Signed-off-by: NeilBrown <neilb@suse.de>
* Fix tests sh too many arguments warningsGilles Espinasse2012-10-11
| | | | | | | | Signed-off-by: Gilles Espinasse <g.esp@free.fr> Add quotes on if [ $sum != $sum1 ] Fix 2 typo /sh1sum/sha1sum/ /matc /match / Signed-off-by: NeilBrown <neilb@suse.de>
* raid6check: Auto-repair modeRobert Buchholz2012-09-10
| | | | | | | | When calling raid6check in regular scanning mode, specifiying "autorepair" as the last positional parameter will cause it to automatically repair any single slot failes it identifies. Signed-off-by: NeilBrown <neilb@suse.de>
* raid6check: Repair mode used geo_map incorrectlyRobert Buchholz2012-09-10
| | | | | | | | | In repair mode, the data block indices to be repaired were calculated using geo_map() which returns the disk slot for a data block index and not the reverse. Now we simply store the reverse of that calculation when we do it anyway. Signed-off-by: NeilBrown <neilb@suse.de>
* 07reshape5intr: Set speed_limit_min to be able to reduce resync speed below 1000Jes Sorensen2012-08-13
| | | | | | | | We need to set speed_limit_min accordingly, otherwise setting speed_limit_max below 1000 will have no effect. Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
* tests/03r5assemV1: reduce sync speed further.NeilBrown2012-08-13
| | | | | | | | | | | | This test is quite sensitive to resync speed - if the resync happens to quickly it fails because it sees aan optimal array when it expects a degraded array. 1000 is often slow enough but now always, so slow it down even more. This requires reducing speed_limit_min also as kernel ignores 'max' when speed is below 'min'. Reported-by: Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-25 03:29:29 +0000