So, the issue was raised in 2010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593625#25
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590665#20 and the resolution was made that the udev script should NOT delete the database, which was reflected in udev's ChangeLog (then it was a separate package yet): === udev (167-1) unstable; urgency=medium * New upstream release. * Do not delete the database created by the initramfs udev, for the benefit of newer versions of lvm. This Breaks dmsetup << 2.02.84-1. See #590665 and #593625. * Switch to the gir 1.2 format, courtesy of Emilio Pozuelo Monfort. (Closes: #620335) * Actually enable support for persistent names of virtio block devices introduced in 166-1. (Closes: #617658) * Changed net.agent to invoke a systemd event instead of running ifup when systemd is active. (Closes: #610871) * Clarify in README.Debian that $NEED_PERSISTENT_NET must be exported there as well. (Closes: #618420) * The udev package becomes Multi-Arch: foreign. -- Marco d'Itri <m...@linux.it> Mon, 04 Apr 2011 03:03:03 +0200 === BUT! Then suddenly in a month the urge for the base cleanup is back: === udev (169-1) unstable; urgency=medium * New upstream release. Fixes: + udevadm settle being unreliable at early boot time. (Closes: #624010) * Use "udevadm control --exit" in the initramfs instead of manually killing each udevd process. (Closes: #624469) * Init script: clean up the initramfs udev database even when it is in /run/. (Closes: #626873) -- Marco d'Itri <m...@linux.it> Thu, 19 May 2011 23:14:56 +0200 === I'm just out of words, honestly. The renowned distro at its best.
