Skip to content
New issue

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

fix(dm): remove 59-persistent-storage-dm.rules (bsc#1232063) (SLFO) #382

Merged

Conversation

aafeijoo-suse
Copy link
Collaborator

59-persistent-storage-dm.rules has been obsolete for a long time. The blkid builtin is run from 13-dm.rules. The "dmsetup info" call in this file is actually harmful, because it overrides properties that have already been set in 10-dm.rules, in particular DM_SUSPENDED, to which it assigns a string like "Active" or "Suspended", whereas the stock DM rules and systemd rules expect the property to have the value "0", or "1", respectively.

Signed-off-by: Martin Wilck [email protected]
(cherry picked from commit dracut-ng/dracut-ng@d2ade8a)

mwilck and others added 2 commits November 1, 2024 07:35
59-persistent-storage-dm.rules has been obsolete for a long time.
The blkid builtin is run from 13-dm.rules. The "dmsetup info" call
in this file is actually harmful, because it overrides properties
that have already been set in 10-dm.rules, in particular DM_SUSPENDED,
to which it assigns a string like "Active" or "Suspended", whereas
the stock DM rules and systemd rules expect the property to have
the value "0", or "1", respectively.

Signed-off-by: Martin Wilck <[email protected]>
(cherry picked from commit dracut-ng/dracut-ng@d2ade8a)
Copy link
Collaborator

@tblume tblume left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@aafeijoo-suse aafeijoo-suse merged commit 850d981 into openSUSE:SLFO_Main Nov 4, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants