diff options
| author | Jes Sorensen <Jes.Sorensen@redhat.com> | 2012-05-30 10:45:27 +1000 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2012-05-30 10:45:27 +1000 |
| commit | 451e30b1e6961539467ea3a2f092d5814a7867ca (patch) | |
| tree | 3515b296f2d5ebd79089e5693d525470e920dc54 /tests/05r1-add-internalbitmap-v1c | |
| parent | fc092254a15f130f3ca1a15342b91534a3c4c24e (diff) | |
New tests testing the addition of bitmaps
This set of tests verifies that it is possible to add an internal
bitmap to an existing array, and that the device can be written to
after the bitmap is added. This should catch cases such as the one
fixed by 4474ca42e2577563a919fd3ed782e2ec55bf11a2
Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'tests/05r1-add-internalbitmap-v1c')
| -rw-r--r-- | tests/05r1-add-internalbitmap-v1c | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/tests/05r1-add-internalbitmap-v1c b/tests/05r1-add-internalbitmap-v1c new file mode 100644 index 00000000..7b397844 --- /dev/null +++ b/tests/05r1-add-internalbitmap-v1c @@ -0,0 +1,20 @@ +# +# create a raid1 without any bitmap, add the bitmap and then write to +# the device. This should catch the case where the bitmap is created +# but not reloaded correctly, such as the case fixed by +# 4474ca42e2577563a919fd3ed782e2ec55bf11a2 +# +mdadm --create --run $md0 --metadata=1.2 --level=1 -n2 --delay=1 $dev1 $dev2 +check wait +check nobitmap +testdev $md0 1 $mdsize1b 64 +mdadm -Gb internal --bitmap-chunk=4 $md0 +check bitmap +testdev $md0 1 $mdsize1b 64 +mdadm -S $md0 + +# Re-assemble the array and verify the bitmap is still present +mdadm --assemble $md0 $dev1 $dev2 +check bitmap +testdev $md0 1 $mdsize1b 64 +mdadm -S $md0 |