We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should consider removing these 2 udev rules:
10-mkosi-initrd-dm.rules is no longer necessary since 10-dm-rules sets the db_persist option (https://gitlab.com/lvmteam/lvm2/-/commit/eb4f744820832aff3d6da1bba14f12e91a5b3535).
10-dm-rules
db_persist
Regarding 10-mkosi-initrd-md.rules, it does the same as 63-md-raid-arrays.rules (https://github.com/md-raid-utilities/mdadm/blob/main/udev-md-raid-arrays.rules), also included in the initrd, except setting db_persist. This option was set by @prajnoha in the dracut's matching 59-persistent-storage-md.rules with the addition of 69-dm-lvm-metad.rules (dracutdevs/dracut@b874d4b) to fix LVM on md activation (year 2013), but this rule is not added anymore (dracutdevs/dracut@50e7466) and it was also replaced by 69-dm-lvm.rules (https://gitlab.com/lvmteam/lvm2/-/commit/67722b312390cdab29c076c912e14bd739c5c0f6) and removed from lvm2 (https://gitlab.com/lvmteam/lvm2/-/commit/042fbd43d25f4cc69ceec1aea4d0658bec54b6e3).
63-md-raid-arrays.rules
59-persistent-storage-md.rules
69-dm-lvm-metad.rules
69-dm-lvm.rules
I had not any problem booting LVM on top of RAID using initrds generated by mkosi without the 2nd udev rule, but maybe I'm missing a specific case.
@prajnoha, @teigland, could any of you confirm if it is still required to set db_persist for LVM on md devices? In that case, a PR can be submitted here https://github.com/md-raid-utilities/mdadm, so we can safely remove the 2nd rule.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We should consider removing these 2 udev rules:
10-mkosi-initrd-dm.rules is no longer necessary since
10-dm-rules
sets thedb_persist
option (https://gitlab.com/lvmteam/lvm2/-/commit/eb4f744820832aff3d6da1bba14f12e91a5b3535).Regarding 10-mkosi-initrd-md.rules, it does the same as
63-md-raid-arrays.rules
(https://github.com/md-raid-utilities/mdadm/blob/main/udev-md-raid-arrays.rules), also included in the initrd, except settingdb_persist
. This option was set by @prajnoha in the dracut's matching59-persistent-storage-md.rules
with the addition of69-dm-lvm-metad.rules
(dracutdevs/dracut@b874d4b) to fix LVM on md activation (year 2013), but this rule is not added anymore (dracutdevs/dracut@50e7466) and it was also replaced by69-dm-lvm.rules
(https://gitlab.com/lvmteam/lvm2/-/commit/67722b312390cdab29c076c912e14bd739c5c0f6) and removed from lvm2 (https://gitlab.com/lvmteam/lvm2/-/commit/042fbd43d25f4cc69ceec1aea4d0658bec54b6e3).I had not any problem booting LVM on top of RAID using initrds generated by mkosi without the 2nd udev rule, but maybe I'm missing a specific case.
@prajnoha, @teigland, could any of you confirm if it is still required to set
db_persist
for LVM on md devices? In that case, a PR can be submitted here https://github.com/md-raid-utilities/mdadm, so we can safely remove the 2nd rule.The text was updated successfully, but these errors were encountered: