Multipath architecture.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi.

Can someone spare a little time to help me understand the multipath
utility and daemon a little better?

I read myself through the available documentation. The refbook says that
it's multipath who's creating maps, and multipathd responsible for path
checking.

Running multipath (at least the version 0.4.7 I've got here), this
actually doesn't seem to be the case. Unless I'm totally mistaken,
multipathd actually does create DM maps as paths are discovered. And not
just fork/exec the utility as many sources (most notably the man page)
state.

No, I'm not asking for general advice on how old documentation relates
to new code. :)

My question here would be rather: Everywhere I've been looking at until
now there's seems to be a multipath %M:%m being run from udev. In
addition to the running daemon.

Is this redundant or does the run from udevd still add some major value?

Cheers,
Daniel 

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

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux