UPSTREAM: dm thin: set minimum_io_size to pool's data block size
Before, if the block layer's limit stacking didn't establish an
optimal_io_size that was compatible with the thin-pool's data block size
we'd set optimal_io_size to the data block size and minimum_io_size to 0
(which the block layer adjusts to be physical_block_size).
Update pool_io_hints() to set both minimum_io_size and optimal_io_size
to the thin-pool's data block size. This fixes an issue reported where
mkfs.xfs would create more XFS Allocation Groups on thinp volumes than
on a normal linear LV of comparable size, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1003227
BUG=chromium:766786
TEST=build/boot on samus, xfstest generic/405 passes
Change-Id: If472aa86daa1745d4a12dab72aab84eb4833a9ad
Reported-by: Chris Murphy <lists@colorremedies.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
(cherry picked from commit fdfb4c8c1a9fc8dd8cf8eeb4e3ed83573b375285)
Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/696554
Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
1 file changed
