[Bug 1570580] Re: Existing Logical Volumes on multipathed SCSI disks are not automatically activated during installation

[Dimitri John Ledkov]

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://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451535

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)

** Bug watch added: Debian Bug tracker #451535
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451535

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1570580

Title:
  Existing Logical Volumes on multipathed SCSI disks are not
  automatically activated during installation

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in debian-installer package in Ubuntu:
  Incomplete

Bug description:
  Installer version: 447
  Kernel: 4.4.0.18
  Description/Reproduction:
  Logical Volumes that exist on multipathed SCSI disks from a previous installation are not automatically activated and thus can not be reused. Only the partitions are visible and that their type is "lvm" (s. screenshot). 

  Workaround:

  When the partitioned disks are shown in the "Partition disks" menu,
  open a shell. Then list all logical volumes with command lvs, and set
  each logical volume active with lvchange -ay
  <volumegroupname>/<lvolname>. Choose "Configure the Logical Volume
  Manager", confirm keeping current partition layout with "Yes"  and
  "Finish" without changing anything. Then the Logical Volumes are
  displayed in the "Partition disks" menu and filesystems can be created
  and mountpoints defined.

  I will attach syslog and partman of the installation attempt.

  So obviously an lvchange -ay on all detected lolgical volumes is
  missing at the proper time....

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570580/+subscriptions