Right, this is a multipath-tools problem (AFAIK regression).. not aware
of any new ioctl requirements that a newer multipathd would have to
warrant the stricter use of a newer DM ioctl version.
Mike
On Wed, Sep 19 2018 at 11:30am -0400,
Özkan Göksu wrote:
>Hello.
>After your mail I
Hello.
After your mail I tried something;
I just curious what will happen when I downgrade multipath-tools package
and the rest was latest.
lvm2 2.02.181-1
device-mapper 2.02.181-1
I just downgrade to: multipath-tools 0.7.6-1
Everything works great. I didnt saw any problem.
I was thinking the
On Wed, Sep 19 2018 at 8:52am -0400,
Zdenek Kabelac wrote:
> Dne 19.9.2018 v 12:35 Özkan Göksu napsal(a):
> >Hello.
> >I just upgraded my Kernel to: 4.14.70-1-lts | device-mapper
> >2.02.181-1 | multipath-tools 0.7.7-1
> >After that multipathd started to giving the log: // device-mapper:
>
Dne 19.9.2018 v 12:35 Özkan Göksu napsal(a):
Hello.
I just upgraded my Kernel to: 4.14.70-1-lts | device-mapper 2.02.181-1 |
multipath-tools 0.7.7-1
After that multipathd started to giving the log: // device-mapper: ioctl:
ioctl interface mismatch: kernel(4.37.0), user(4.39.0), cmd(16)
It was
Thank you for your answer.
I will report the issue to arch-linux team.
Regards.
Heinz Mauelshagen , 19 Eyl 2018 Çar, 14:48 tarihinde
şunu yazdı:
> Özkan,
>
> as you report, your device-mapper version is too recent for your kernel
> (the major version has to match and the kernel minor version
Özkan,
as you report, your device-mapper version is too recent for your kernel
(the major version has to match and the kernel minor version needs to
greater or equal),
i.e. 4.39 is too recent for version 4.37 in the kernel.
In case you updated kernel and userspace by pacman means, something's
Hello.
I just upgraded my Kernel to: 4.14.70-1-lts | device-mapper 2.02.181-1 |
multipath-tools 0.7.7-1
After that multipathd started to giving the log: // device-mapper: ioctl:
ioctl interface mismatch: kernel(4.37.0), user(4.39.0), cmd(16)
It was working great on my ex kernel "4.14.30-1-lts"
