On Wed, Nov 25, 2020 at 03:17:42PM +0800, Anand Jain wrote:
On 25/11/20 9:57 am, Naohiro Aota wrote:
On Tue, Nov 24, 2020 at 07:36:18PM +0800, Anand Jain wrote:
On 10/11/20 7:26 pm, Naohiro Aota wrote:
This commit implements a zoned chunk/dev_extent allocator. The zoned
allocator aligns the device extents to zone boundaries, so that a zone
reset affects only the device extent and does not change the state of
blocks in the neighbor device extents.
Also, it checks that a region allocation is not overlapping any of the
super block zones, and ensures the region is empty.
Signed-off-by: Naohiro Aota <naohiro.aota@xxxxxxx>
Looks good.
Chunks and stripes are aligned to the zone_size. I guess zone_size won't
change after the block device has been formatted with it? For testing,
what if the device image is dumped onto another zoned device with a
different zone_size?
Zone size is a drive characteristic, so it never change on the same device.
Dump/restore on another device with a different zone_size should be banned,
because we cannot ensure device extents are aligned to zone boundaries.
Fair enough. Do we have any checks to fail such mount? Sorry if I have
missed it somewhere in the patch?
Thanks.
We have a check in verify_one_dev_extent() to confirm that a device
extent's position and size are aligned to zone size (patch 13).
