Your message dated Sat, 26 Apr 2014 13:37:05 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-systemd-maintainers] Bug#745390: systemd: fails to
recognize that LVM2 device nodes are already present and accessible
has caused the Debian Bug report #745390,
regarding systemd: fails to recognize that LVM2 device nodes are already
present and accessible
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
745390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745390
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 204-8
In my custom initramfs, the device nodes for /dev/vg0/home and /dev/vg0/swap
are created. After the boot process is handed over to systemd, it enters an
emergency shell: The (autogenerated) [email protected] and
[email protected] want dev-vg0-home.device and
dev-vg0-swap.device to be ready, but "systemctl status dev-vg0-home.device"
and "systemctl status dev-vg0-swap.device" shows they are inactive -- even
though the device nodes at /dev/vg0/home and /dev/vg0/swap actually exists!
A workaround for this bug was to create dummy device units:
$ touch /etc/systemd/system/dev-vg0-home.device
$ touch /etc/systemd/system/dev-vg0-var.device
lvm2 is at version 2.02.104-2, so the issue noted at
https://wiki.debian.org/systemd (which is said to be solved in lvm2 >=
2.02.104-1 ) seems to be different.
Many thanks for taking a look at this issue.
Best,
Dominik
--- End Message ---
--- Begin Message ---
Hi Dominik,
Dominik Brodowski <[email protected]> writes:
> In my custom initramfs, the device nodes for /dev/vg0/home and /dev/vg0/swap
> […]
Thanks for your report.
Unfortunately, due to limited manpower, we cannot support custom
initramfs setups. Feel free to reopen this bug in case you can reproduce
it with the standard initramfs.
Of course you are welcome to debug this issue yourself and send us a
patch to fix the issue.
Thanks for your understanding.
--
Best regards,
Michael
--- End Message ---
