Merge ~bladernr/plainbox-provider-checkbox:1467520-disk-tests-mapper-devs into plainbox-provider-checkbox:master
Proposed by
Jeff Lane
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Paul Larson | ||||
Approved revision: | 3f5eaf35e8d78d2b01d75bb2f9c03872df45f82e | ||||
Merged at revision: | 6f0cb0155bc146431ee060d63cf9a46481a12014 | ||||
Proposed branch: | ~bladernr/plainbox-provider-checkbox:1467520-disk-tests-mapper-devs | ||||
Merge into: | plainbox-provider-checkbox:master | ||||
Diff against target: |
152 lines (+89/-19) 2 files modified
bin/disk_stress_ng (+22/-7) bin/storage_test (+67/-12) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Paul Larson | Approve | ||
Jeff Lane | Needs Resubmitting | ||
Review via email: mp+323189@code.launchpad.net |
Description of the change
Modified disk_stress_ng to work with devmapper devices.
Tested with xenial and zesty on Power8
To post a comment you must log in.
A couple of minor comments, and a question. Does this really make sense for selecting a disk to run a destructive test on? Would it be better to either 1. insist that we have a configured value for the disk we can use for this, or 2. Look for the largest *unmounted" partition that is also not part of a mounted logical volume that is mounted?
I see this is a pretty critical bug though, so if you can address these things, great. But they are not worth blocking on if you need to land this and it's well tested. I don't think I have a way to really test it myself, but I saw that you had commented on the tests done with it.