Re: multipath-tools 0.7.4 failure to remove device

[Martin Wilck <mwilck@suse.com>]

On Fri, 2018-01-12 at 22:47 +0100, Julian Andres Klode wrote:
> 
> I don't know actually, I'm just updating the package :) 

The feature needs to be enabled explicitly, so indeed you weren't using
it.

> >I can say that
> the tests were run with default configuration, normally we run with
> DEFAULT_FIND_MULTIPATHS but that does not work yet with 0.7.4 - no
> dm-0 device seems to get created in this test case (some systems
> without
> multipath were broken 2.5 years ago just by installing it because it
> took over non-multipath devices, hence the option was enabled; might
> not even be needed anymore).

That's still the default behavior if find_multipaths is off. And
actually, I don't know what's wrong with that. If you don't like it,
blacklist your root device. All you need to make sure is that multipath
settings in the initrd and in the booted system are the same.

"find_multipaths" is not a silver bullet to kill off multipath-related
boot problems. It has advantages and disadvantages, depending on the
use case. Anyway, I'm not aware of general problems with it in the
later multipath versions.

Btw, one thing you should be aware of is that udev rule files and
systemd service files have changed. That requires also dracut changes
that are not in upstream dracut yet.

Regards,
Martin

-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel