Sat Mar 5 19:55:20 UTC 2022
-s, --physicalextentsize PhysicalExtentSize[kKmMgGtT]
Sets the physical extent size on physical volumes
of this volume group. A size suffix (k for kilo<AD>
bytes up to t for terabytes) is optional, megabytes
is the default if no suffix is present. Values can
be from 8 KB to 16 GB in powers of 2. The default
of 4 MB causes maximum LV sizes of ~256GB because
as many as ~64k extents are supported per LV. In
case larger maximum LV sizes are needed (later),
you need to set the PE size to a larger value as
well. Later changes of the PE size in an existing
VG are not supported.
Things to note when setting up your PE size, you cannot change this value
LATER so setting a bigger number is better, setting a bigger number is
less efficent with your disk space as odd fractions at the end below the
PE size will be lost. lvm reserves one of your PEs for itself, so to
large a size can be bad.
A large size sets the minimum partition size you can create in my example
32mb I can live with that...
A large size reduces the total table size for a PE (for a give ammount of
disk space), so reduces the lookup time, and increase the ablitity for
the processor to fit more of it in processor cache, thereby giving fast
Setting this value is a "magic" I would suggest for "home" use a value of
16m or 32m is quite appropriate,, but the choice is yours. Its best to
over estimate than under-estimate. If you fill the vg table with PEs you
cannot extend it later.....
More information about the linux-lvm