Bug#689605: multipath-tools: no default multipath.conf

Ritesh Raj Sarraf rrs at researchut.com
Thu Oct 4 16:02:37 UTC 2012

On Thursday 04 October 2012 06:57 PM, Andreas Pflug wrote:
> Since the multipath-tools package includes no standard multipath.conf, multipathd will grab any new block device. This can lead to surprising and hard debug effects.
> e.g. attaching a device in a XEN dom0 domain will render the device inaccessible. This corrupts xen-utils-4.1 since xend will attach the boot device locally for pygrub, but can't release it properly because multipathd has it.
> I suggest supplying at least a minimal multipath.conf that blacklists the most dangerous devices by default.
> -- Package-specific info:
> Contents of /etc/multipath.conf:
> blacklist
> {
> 	devnode "^xvd[0-9a-z]*"
> }

Thanks. That is a good point. But it'd make more sense to ship the
default file with
                    devnode "*"

And then let the user pick up his/her choice of settings.
That way, it'd cover everything. Virtual block devices, Pluggable
portable dists etc.

Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20121004/918335a5/attachment.pgp>

More information about the pkg-lvm-maintainers mailing list