* Sergey Aleynikov <sergey.aleyni...@gmail.com> [241208 20:02]: > > If dmsetup_env helps with anything, then you found some other > > package's udev rules relying on extremely outdated stuff. > > > > dmsetup_env should have exported DM_NAME, DM_UUID, DM_STATE=ACTIVE, > > DM_TABLE_STATE=LIVE. DM_NAME and DM_UUID should be exported by the > > dmsetup udev helper (from src:lvm2). > > I've generated a list of all files in /lib/udev/rules.d mentioning > DM_* variables with the following script: > > ack -c DM_ /lib/udev/rules.d/|grep -v ':0'|cut -d: -f1|xargs -n1 dpkg -S > kpartx: /lib/udev/rules.d/68-del-part-nodes.rules > dmsetup: /lib/udev/rules.d/55-dm.rules > dmsetup: /lib/udev/rules.d/95-dm-notify.rules > systemd: /lib/udev/rules.d/99-systemd.rules > lvm2: /lib/udev/rules.d/56-lvm.rules > lvm2: /lib/udev/rules.d/69-lvm.rules > kpartx: /lib/udev/rules.d/60-kpartx.rules > dmsetup: /lib/udev/rules.d/60-persistent-storage-dm.rules > kpartx: /lib/udev/rules.d/56-dm-parts.rules > > Than I proceeded to compare the content of all those files with > originals from the respected packages, and the only different found > was my modification of reverting a single line in 60-kpartx.rules, so > if there is a some obsolete usage it's packaged with boorkworm.
> Should > this report be then moved to lvm2? Maybe, maybe not. ISTM you'll need to debug why adding dmsetup_env changes anything. Maybe there's some form of race and having dmsetup_env just changes the timing. Chris
