© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
5466644
demo site
(Get the code!)
I based my comment on extensive knowledge of the debian-installer / partman source code =)
There are bug reports about it open in debian BTS, e.g. https:/
And do note that this is during the debian-installer, post-install system can access and active whichever lvm groups/volumes desired and be setup as mountpoints in /etc/fstab as desired. Similarly, one can preseed arbitrary shell commands to achieve similar either as post installation exec commands, or partman early. But that's not declarative preseed syntax to e.g. active this group, reuse that volume.
I am more interested in production deployment examples that reuse volume groups across multiple different distributions and how zipl/boot is managed on those scenarios.
Or is this request to active volume groups just to prevent data-loss?
Activated volume groups, would put block devices in use, potentially preventing them from being formatted. (That is especially the case if only partial number of physical devices are activated of a particular volume group)