From 51e90d49bae0a1d92687876f161c8463529fb702 Mon Sep 17 00:00:00 2001 From: Zdenek Kabelac Date: Mon, 6 Mar 2023 14:52:59 +0100 Subject: [PATCH 099/115] vdo: use fixed size vdopool wrapper Instead of using size of 'empty header' in vdopool use fixed size 4K for a 'wrappeing' vdo-pool device. This fixes the issue when user tried to activate vdo-pool after a conversion from vdo managed device with 'vgchange -ay' - where this command activated all LVs with 'vdo-pool' wrapping device as well, but this converted pool uses 0-length header. This 4k size should usually prevent other tools like 'blkid' recognize such device as anything - so it shouldn't cause any problems with duplicate indentification of devices. (cherry picked from commit e8e6347ba3f59cbd2f7e92aa707543b90fa607a3) --- lib/activate/dev_manager.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/activate/dev_manager.c b/lib/activate/dev_manager.c index 4924d8c56..0c029917f 100644 --- a/lib/activate/dev_manager.c +++ b/lib/activate/dev_manager.c @@ -3043,7 +3043,7 @@ static int _add_layer_target_to_dtree(struct dev_manager *dm, /* Add linear mapping over layered LV */ /* From VDO layer expose ONLY vdo pool header, we would need to use virtual size otherwise */ - if (!add_linear_area_to_dtree(dnode, lv_is_vdo_pool(lv) ? first_seg(lv)->vdo_pool_header_size : lv->size, + if (!add_linear_area_to_dtree(dnode, lv_is_vdo_pool(lv) ? 8 : lv->size, lv->vg->extent_size, lv->vg->cmd->use_linear_target, lv->vg->name, lv->name) || -- 2.41.0