Assertion failure while running removal_with_ganging test with 4K devices
We hit a panic in the removal_with_ganging test using vdevs with 4k ashift for testing.
The problem is that the test intentionally induces ganging in allocations as small as 4K, but failing a minimum-size allocation (4K in this case) is not permitted. We should change the test to only gang 8K and larger, or make it dynamic based on the max ashift in the pool.
Updated by Electric Monk about 2 years ago
- % Done changed from 0 to 100
- Status changed from New to Closed
commit 243952c7eeef020886e3e2e3df99a513df40584a Author: Matt Ahrens <Matt.Ahrens@delphix.com> Date: 2018-03-21T15:26:16.000Z 9280 Assertion failure while running removal_with_ganging test with 4K devices Reviewed by: George Wilson <firstname.lastname@example.org> Reviewed by: John Kennedy <email@example.com> Approved by: Garrett D'Amore <firstname.lastname@example.org>