[dm-devel] [PATCH] libmultipath: check if adopt_path() really added current path
Martin Wilck
mwilck at suse.com
Wed Feb 3 13:14:09 UTC 2021
On Wed, 2021-02-03 at 17:42 +0800, lixiaokeng wrote:
>
>
> On 2021/2/3 16:14, Martin Wilck wrote:
> > Is this also a Tested-by:?
> > IOW, did it fix your issue?
>
> Yes, it solves the crash.But there is an other issue.
>
> multipath.conf
> defaults {
> find_multipaths no
> }
>
> [root at localhost coredump]# multipathd add path sdb
> fail
> [root at localhost coredump]# multipath -ll
> [root at localhost coredump]# multipathd add path sdb
> ok
> [root at localhost coredump]# multipath -ll
> 0QEMU_QEMU_HARDDISK_drive-scsi0-0-0-1 dm-3 QEMU,QEMU HARDDISK
> size=1.0G features='0' hwhandler='0' wp=rw
> `-+- policy='service-time 0' prio=1 status=enabled
> `- 2:0:0:1 sdb 8:16 active ready running
>
> I add local path twice. The first fails while the second
> succeeds.
More details please. What exactly were you doing? Was this a regression
caused by my patch? Please provide multipathd -v3 logs.
Also, you're aware that "find_multipaths no" is discouraged?
It leads to inconsistent behavior between multipath and multipathd.
Regards,
Martin
More information about the dm-devel
mailing list