Package: dmraid
Version: 1.0.0.rc16-12
Hello,
dmraid has an issue where kpartx is not run on boot.
This is due to the udev rule being triggered by DM_STATE, which is no
longer set. It used to be set by multipath-tools, but no longer does
since multipath-tools version 0.8.8-1[0].
What this means is that dmraid will work so you can see the block
device itself, but upon boot no partitions will be shown, and users
will have to manually run kpartx. This is the good case when the
partition is not the boot drive, if a user is using the latest
multipath-tools and dmraid for a boot drive, the partitions will not
be seen and fail to boot.
We can either reinstate the env file, or change the trigger. I'm
thinking about changing the trigger which looks like:
diff --git a/debian/dmraid.udev b/debian/dmraid.udev
index a4a1ab7..407d57b 100644
--- a/debian/dmraid.udev
+++ b/debian/dmraid.udev
@@ -4,5 +4,5 @@
SUBSYSTEM=="block", ACTION=="add", ENV{ID_TYPE}=="disk",
ENV{ID_FS_USAGE}=="raid", KERNEL=="hd[a-z]|sd[a-z]", \
RUN+="/sbin/dmraid-activate %k"
-ENV{DM_STATE}=="ACTIVE", ENV{DM_UUID}=="DMRAID-*", \
- RUN+="/sbin/kpartx -a /dev/$kernel"
\ No newline at end of file
+ENV{DM_ACTIVATION}=="1", ENV{DM_UUID}=="DMRAID-*", \
+ RUN+="/sbin/kpartx -a /dev/$kernel"
Relevant Ubuntu bug [1].
[0] -
https://salsa.debian.org/linux-blocks-team/multipath-tools/-/commit/4ab9ce259ffa75ed3e2d145b3f2effc22af7b4c6
[1] - https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/2047303
