Package Details: multipath-tools 0.7.4-1

Git Clone URL: https://aur.archlinux.org/multipath-tools.git (read-only)
Package Base: multipath-tools
Description: Multipath tools for Linux (including kpartx)
Upstream URL: http://christophe.varoqui.free.fr/
Licenses: GPL2
Conflicts: multipath-tools-git
Submitter: xyproto
Maintainer: Bevan
Last Packager: Bevan
Votes: 79
Popularity: 1.275385
First Submitted: 2013-01-24 14:33
Last Updated: 2017-11-15 23:20

Dependencies (7)

Sources (1)

Latest Comments

Bevan commented on 2018-01-06 18:08

I think you can also add specific devices to your blacklist exception. The fact that LVM uses the devices before multipath can may suggest that adding some directives to the systemd service so that lvm only starts after multipathd may also help.

But to be honest, I have only very limited own experience with multipath setups. Maybe you should ask on the dm-devel mailing list about this.

jab416171 commented on 2018-01-06 17:06

I tried adding that, and now this is my blacklist_exceptions (output from multipath -t):

blacklist_exceptions { property "(SCSI_IDENT_.*|ID_WWN)" property "(SCSI_IDENT_|ID_WWN)" }

After rebooting, I only get 2 multipath devices that show up. There were 6 before I rebooted. The other LUNs show up, but just the individual partitions, not the "alias" I defined in multipath.conf.

Actually upon closer inspection, it appears lvm is finding and opening the devices before multipath can.

Bevan commented on 2018-01-06 10:04

jab416171: Have a look at the section "blacklist_exceptions section" in man multipath.conf. I guess your devices are missing the SCSI_IDENT_.* property. However, this is required since 0.6.0 already so I'm not sure why you didn't have the issue with 0.6.4: https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commitdiff;h=d041591e42b69e2ff99d9cc5c1111c83ccde3207

RedHat disables this blacklisting in their distributions:

0004-RH-Remove-the-property-blacklist-exception-builtin.patch: Allow multipath to be used on devices without multiple paths. NAK'ed upstream, but requested by Red Hat

Since you can easilly change this behavior via blacklist_exceptions in multipath.conf, I wouln't like to deviate from upstream here though.

jab416171 commented on 2018-01-06 06:59

I just updated from 0.6.4 to 0.7.4, and now only two of my LUNs are showing up. There should be about 16. multipath -v3 -ll mentions this: dm-x: blacklisted, udev property missing (once for each LUN). Two of the LUNs do work, interestingly, even though they are also 'blacklisted'.

Bevan commented on 2017-11-12 12:48

On requiring systemd:

As far as I can see, the only additional feature is the systemd integration itself. If this was a package in the official repos, adding systemd as dependency would probably be the right thing to do. Here in AUR it depends on whether there are more people running their systems without systemd or more people with systemd building this package in a clean chroot. My gut feeling is that the first group is larger, so I have added systemd as an optional dependency only.

Enabling multipathd.{service,socket} fails:

Running "systemctl enable multipathd.service" currently fails because multipathd.socket is lacking an [Install] section. This is an upstream issue which will be reported soon.

Bevan commented on 2017-10-19 20:53

daniel_shub: Thanks for the hint! Although this package does not require systemd, it probably provides some additional functionality if systemd is installed while building. I will have a look at this (probably not before next week).

Although, if the additional functionality is limited, it may be a good idea to leave systemd as an optional dependency for those who want it (as it is currently the case for ceph).

daniel_shub commented on 2017-10-19 20:13

Although systemd is included in the base group and therefore does not need to be included in depends, it is not in the base-devel group and therefore does need to be included in makedepends to enable the package to be built in a clean chroot: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

Bevan commented on 2017-09-30 20:29

alaricljs: Thanks for the report! This is an upstream bug which should be easy to fix. I added a corresponding patch. Could you please confirm that it solves the issue?

alaricljs commented on 2017-09-30 17:31

Don't know if this is upstream but the build dies on me because I have a Samba domain, previous versions have worked.

ln -sf libdmmp.so.0.1.0 libdmmp.so
install: creating directory 'docs/man'
'docs/libdmmp.h.3' -> 'docs/man/libdmmp.h.3'
cat libdmmp/libdmmp.h | \
perl docs/doc-preclean.pl > /tmp/MYDOMAIN\mylogin/tmp.VAFmG0J7Zh
/bin/sh: line 1: /tmp/MYDOMAINmylogin/tmp.VAFmG0J7Zh: No such file or directory

I obfuscated my domain and login, but as you can see since there is a \ it needs to be quoted or escaped.

Case_Of commented on 2017-09-20 20:45

@Bevan: It works now, thanks. And you're right, I do not have systemd here.

All comments