7b41368fc3c2ab1ce5b94a8ae62a38b295e6361e
As reported in the community forum [0], there currently is a warning from LVM when converting to a base image on an LVM-thin storage: > WARNING: Combining activation change with other commands is not advised. From a comment in the LVM source code: > Unfortunately, lvchange has previously allowed changing an LV > property and changing LV activation in a single command. This was > not a good idea because the behavior/results are hard to predict and > not possible to sensibly describe. It's also unnecessary. So, this > is here for the sake of compatibility. > > This is extremely ugly; activation should always be done separately. > This is not the full-featured lvchange capability, just the basic > (the advanced activate options are not provided.) > > FIXME: wrap this in a config setting that we can disable by default > to phase this out? While it's not clear there's an actual issue in the specific use case here, just follow what LVM recommends for future-proofing. [0]: https://forum.proxmox.com/threads/165279/ Signed-off-by: Fiona Ebner <f.ebner@proxmox.com> Link: https://lore.proxmox.com/20250422133314.60806-1-f.ebner@proxmox.com
Description
with PMEM support!
Languages
Perl
99.3%
Makefile
0.6%