Below is the current draft of a resolution to resolve 728486. I have one current comment in the draft which I would like clarified. [CTTE members: please comment/suggest change.] I also expect to change the reference to the patch to a newly updated patch with the changes suggested in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728486#183.
==BEGIN DRAFT== When systemd is in operation in conjunction with lvm and lvmetad is not in use, lvchange -aay must be called after udevadm --settle which is provided by systemd-udev-settle.service, and before (and after) encrypted devices are configured (cryptsetup.target). ==COMMENT== Is there any case where udevadm --settle would be required after the encrypted devices are configured? Does cryptsetup.target ensure that udev has triggered the appropriate rules for the newly configured encrypted devices? ==END COMMENT== The patch prepared by Michael Stapelberg <[email protected]> in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728486#163 installs the two systemd unit files necessary to properly configure lvm devices when systemd is running, and additionally configures systemd-tmpfiles.d to create the lockfile directories required by systemd. Therefore, the CTTE: A. Overides the objection of the maintainer of lvm (Bastian Blank <[email protected]>) to this patch, and directs the maintainer to accept this patch or alternatively, authorizes an NMU to implement this patch. B. Further discussion ==END DRAFT== This draft is 728486_systemd_and_lvm_incompatibility/draft-dla in git. -- Don Armstrong http://www.donarmstrong.com I may not have gone where I intended to go, but I think I have ended up where I needed to be. -- Douglas Adams _The Long Dark Tea-Time of the Soul_ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
