Description of problem: dev_size in the VG configuration file ("Text Format Volume Group") and the "Not Usable" in `pvdisplay` can change after pvresize. For example, two PVs were created with `--dataalignment 8M` (and then a VG was created with `-s 8M` on them). The partitions are of 7176M each (7G + 8M). Before pvresize, dev_size is equal to 717GM with "Not Usable" being 0. After pvresize (--setphysicalvolumesize 7176M), dev_size is equal to 7GiB with "Not Usable" being 8MiB. Note that pe_start and pe_count remains the same, so this doesn't seem to be a serious problem. Just that it may cause confusion. See the attached files for more details. The states of the PVs are "Before" and "After" respectively. Version-Release number of selected component (if applicable): 2,02.187 How reproducible: Always Steps to Reproduce: 1.Create PV(s) with `--dataalignment` 2.Create a VG on the PVs 3.pvresize the PV(s) Actual results: dev_size and "Not Usable" not being consistent before and after pvresize (when the size is actually the same) Expected results: dev_size and "Not Usable" being consistent before and after pvresize (when the size is actually the same) Additional info:
Created attachment 1734268 [details] pvdisplay
Created attachment 1734269 [details] vgcfg
Btw it seems like a step missing to the PVs or so in vgcreate (and maybe also vgextend/vgreduce), unless the "Before" is considered "correct" (I don't know the "definition" of dev_size but "Not Usable 0" seems wrong to me).